US20210329442A1 - Mobile Gateway - Google Patents
Mobile Gateway Download PDFInfo
- Publication number
- US20210329442A1 US20210329442A1 US17/135,796 US202017135796A US2021329442A1 US 20210329442 A1 US20210329442 A1 US 20210329442A1 US 202017135796 A US202017135796 A US 202017135796A US 2021329442 A1 US2021329442 A1 US 2021329442A1
- Authority
- US
- United States
- Prior art keywords
- access code
- callee
- identifier
- mobile telephone
- call
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 claims abstract description 82
- 230000004044 response Effects 0.000 claims abstract description 28
- 230000000977 initiatory effect Effects 0.000 claims abstract description 18
- 238000004891 communication Methods 0.000 claims description 70
- 230000015654 memory Effects 0.000 description 55
- 230000008569 process Effects 0.000 description 54
- 230000006870 function Effects 0.000 description 18
- 238000010586 diagram Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000010348 incorporation Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/15—Setup of multiple wireless link connections
Definitions
- This invention relates generally to telecommunication, and more particularly to methods, systems, apparatuses, and computer readable media for initiating or enabling a call with a mobile telephone to a callee.
- Mobile telephone service providers often charge significant fees for long distance telephone calls, particularly when the mobile telephone is roaming in another mobile telephone service provider's network.
- a “calling card” may permit the user of the mobile telephone to place a call to a local telephone number or to a less-expensive telephone number (such as a toll-free number, for example) instead of placing the call directly to the callee.
- the user may thus avoid the long distance charges of the mobile telephone service provider, which may be higher than the charges for using the “calling card”.
- this technique can be cumbersome and undesirable, because it may require the user of the mobile telephone to follow a number of complicated or cumbersome steps in order to initiate a call to the callee, for example.
- a method of initiating a call to a callee using a mobile telephone involves receiving, from a user of the mobile telephone, a callee identifier associated with the callee; transmitting an access code request message to an access server, the access code request message including the callee identifier; receiving an access code reply message from the access server in response to the access code request message, the access code reply message including an access code different from the callee identifier and associated with the callee identifier; and initiating a call with the mobile telephone using the access code to identify the callee.
- Transmitting may involve transmitting the access code request message to the access server on a non-voice network.
- Transmitting may involve transmitting a location identifier of a location associated with the mobile telephone to the access server.
- Transmitting the location identifier may involve transmitting an IP address of the mobile telephone in a wireless IP network.
- Transmitting the location identifier may involve transmitting an identifier of a wireless voice signal station in wireless communication with the mobile telephone.
- Transmitting the location identifier may involve transmitting a user-configured identifier of a location associated with the mobile telephone.
- Receiving the access code reply message may involve receiving the access code reply message from the access server on a non-voice network.
- Receiving the access code reply message may involve receiving, in the access code reply message, an access code temporarily associated with the callee identifier.
- Receiving the access code reply message may involve receiving, in the access code reply message, a telephone number identifying a channel operably configured to cooperate with an IP network to cause a call involving the mobile telephone and the callee to be routed through the IP network.
- Initiating the call may involve engaging a routing controller to route the call on the IP network to the callee.
- the method may further involve: receiving from the mobile telephone the access code request message; communicating with a routing controller to obtain from the routing controller the access code wherein the access code identifies a channel and is useable by the mobile telephone to cause the routing controller to establish a call to the callee using the channel; and transmitting the access code reply message to the mobile telephone.
- a mobile telephone includes: provisions for receiving, from a user of the mobile telephone, a callee identifier associated with the callee; transmitting provisions for transmitting an access code request message to an access server, the access code request message including the callee identifier; provisions for receiving an access code reply message from the access server in response to the access code request message, the access code reply message including an access code different from the callee identifier and associated with the callee identifier; and provisions for initiating a call using the access code to identify the callee.
- the transmitting provisions may include a non-voice network interface for transmitting the access code request message to the access server on a non-voice network.
- the access code request message may further include a location identifier of a location associated with the mobile telephone.
- the location identifier may include an IP address of the mobile telephone in a wireless IP network.
- the location identifier may include an identifier of a wireless voice signal station in wireless communication with the mobile telephone.
- the location identifier may include a user-configured identifier of a location associated with the mobile telephone.
- the provisions for receiving an access code reply message may include a non-voice network interface for receiving the access code reply message on a non-voice network.
- the access code may include a telephone number.
- the means for initiating may involve a mobile telephone network interface.
- a system for initiating a call to a callee includes the mobile telephone, a routing controller, and an access server.
- the access server includes: provisions for receiving from the mobile telephone the access code request message; provisions for communicating with the routing controller to obtain from the routing controller the access code wherein the access code identifies a channel and is useable by the mobile telephone to cause the routing controller to establish a call to the callee using the channel; and provisions for transmitting the access code reply message including the access code to the mobile telephone.
- a mobile telephone in accordance with another aspect, there is provided a mobile telephone.
- the mobile telephone includes a processor circuit, a network interface in communication with the processor circuit, and a computer readable medium in communication with the processor circuit and encoded with codes for directing the processor circuit to: receive, from a user of the mobile telephone, a callee identifier associated with the callee; cause an access code request message to be transmitted to an access server, the access code request message including the callee identifier; receive an access code reply message from the access server in response to the access code request message, the access code reply message including an access code different from the callee identifier and associated with the callee identifier; and initiate a call using the access code to identify the callee.
- the network interface may include a non-voice network interface
- the codes for directing the processor circuit to cause the access code request message to be transmitted may include codes for directing the processor circuit to cause the access code request message to be transmitted to the access server using the non-voice network interface on a non-voice network.
- the access code request message may further include a location identifier of a location associated with the mobile telephone.
- the location identifier may include an IP address of the mobile telephone in a wireless IP network.
- the location identifier may include an identifier of a wireless voice signal station in wireless communication with the mobile telephone.
- the location identifier may include a user-configured identifier of a location associated with the mobile telephone.
- the network interface may include a non-voice network interface
- the codes for directing the processor circuit to receive an access code reply message may include codes for directing the processor circuit to cause the access code reply message to be received from the access server using the non-voice network interface on a non-voice network.
- the access code may include a telephone number identifying a channel operably configured to cooperate with an IP network to cause a call involving the mobile telephone and the callee to be routed through the IP network.
- the network interface may include a mobile telephone network interface
- the codes for directing the processor circuit to initiate may include codes for directing the processor circuit to cause a call to be initiated using the mobile telephone network interface on a mobile telephone network.
- a system for initiating a call to a callee includes: the mobile telephone; a routing controller; and an access server comprising a processor circuit and a computer readable medium in communication with the processor circuit.
- the computer readable medium is encoded with codes for directing the processor circuit to: receive from the mobile telephone the access code request message; communicate with the routing controller to obtain from the routing controller the access code wherein the access code identifies a channel and is useable by the mobile telephone to cause the routing controller to establish a call to the callee using the channel; and transmit the access code reply message to the mobile telephone.
- a computer readable medium encoded with codes for directing a processor circuit to: receive, from a user of a mobile telephone, a callee identifier associated with a callee; transmit an access code request message to an access server, the access code request message including the callee identifier; receive an access code reply message from the access server in response to the access code request message, the access code reply message including an access code different from the callee identifier and associated with the callee identifier; and initiate a call using the access code to identify the callee.
- a method for enabling a mobile telephone to initiate a call to a callee through a channel involves: receiving from the mobile telephone an access code request message including a callee identifier associated with the callee; communicating with a routing controller to obtain from the routing controller an access code identifying the channel, the access code being different from the callee identifier and useable by the mobile telephone to initiate a call to the callee using the channel; and transmitting an access code reply message including the access code to the mobile telephone.
- Receiving may involve receiving the access code request message on a non-voice network.
- the method may further involve causing the routing controller to produce the access code.
- Producing may involve selecting the access code from a pool of access codes, where each access code in the pool of access codes identifies a respective telephone number.
- the method may further involve determining a local calling area associated with the mobile telephone.
- Determining may involve accessing a dialing profile associated with the caller, the dialing profile including a location field having contents identifying at least a default location of the caller.
- Determining may involve receiving an IP address of the mobile telephone in a wireless IP network.
- Determining may involve receiving an identifier of a wireless voice signal station in wireless communication with the mobile telephone.
- Determining may involve receiving a user-configured identifier of a location associated with the mobile telephone.
- Selecting may involve selecting an access code in the local calling area associated with the mobile telephone.
- Each access code in the pool of access codes may further identify a respective channel operably configured to cooperate with an IP network to cause a call involving the mobile telephone and the callee to be routed through the IP network.
- the method may further involve causing the routing controller to establish communication through the IP network in response to a call received on the channel.
- Producing may further involve storing a caller identifier associated with the mobile telephone in association with the access code.
- Causing the routing controller to establish communication may involve causing the routing controller to establish communication only if the caller identifier associated with the access code identifies the mobile telephone.
- Producing may further involve storing the callee identifier in association with the access code.
- Producing may further involve searching the pool of access codes for an access code associated with the callee identifier to identify the channel usable by the mobile telephone to initiate a call to the callee.
- Producing may further involve storing, in association with the access code, a timestamp for use in determining when the usability of the access code to initiate a call to the callee will expire.
- Causing the routing controller to establish communication may involve causing the routing controller to establish communication only if the usability of the access code to initiate a call to the callee has not expired.
- Transmitting may involve transmitting the access code reply message on a non-voice network.
- a system for enabling a mobile telephone to initiate a call to a callee through a channel includes: provisions for receiving from the mobile telephone an access code request message including a callee identifier associated with the callee; provisions for communicating with the routing controller to obtain from the routing controller an access code identifying the channel, the access code being different from the callee identifier and useable by the mobile telephone to initiate a call to the callee using the channel; and provisions for transmitting an access code reply message including the access code to the mobile telephone.
- the provisions for receiving may include a non-voice network interface for receiving the access code request message on a non-voice network.
- the system may further include provisions for producing the access code.
- the provisions for producing may include a processor circuit operably configured to select the access code from a pool of access codes, where each access code in the pool of access codes identifies a respective telephone number.
- the processor circuit may be operably configured to determine a local calling area associated with the mobile telephone.
- the processor circuit may be operably configured to determine a local calling area associated with the mobile telephone using a dialing profile associated with the caller, the dialing profile including a location field having contents identifying at least a default location of the caller.
- the processor circuit may be operably configured to determine a local calling area associated with the mobile telephone using an IP address of the mobile telephone in a wireless IP network.
- the processor circuit may be operably configured to determine a local calling area associated with the mobile telephone using an identifier of a wireless voice signal station in wireless communication with the mobile telephone.
- the processor circuit may be operably configured to determine a local calling area associated with the mobile telephone using a user-configured identifier of a location associated with the mobile telephone.
- the processor circuit may be operably configured to select an access code in the local calling area associated with the mobile telephone.
- Each access code in the pool of access codes may further identify a respective channel operably configured to cooperate with an IP network to cause a call involving the mobile telephone and the callee to be routed through the IP network.
- the processor circuit may be operably configured to establish communication through the IP network in response to a call received on the channel.
- the processor circuit may be operably configured to store a caller identifier associated with the mobile telephone in association with the access code.
- the processor circuit may be operably configured to cause the routing controller to establish communication only if the caller identifier associated with the access code identifies the mobile telephone.
- the processor circuit may be operably configured to store the callee identifier in association with the access code.
- the processor circuit may be operably configured to search the pool of access codes for an access code associated with the callee identifier to identify the channel usable by the mobile telephone to initiate a call to the callee.
- the processor circuit may be operably configured to store, in association with the access code, a timestamp for use in determining when the usability of the access code to initiate a call to the callee will expire.
- the processor circuit may operably configured to establish communication only if the usability of the access code to initiate a call to the callee has not expired.
- the provisions for transmitting may include a non-voice network interface for transmitting the access code reply message on a non-voice network.
- a system for enabling a mobile telephone to initiate a call to a callee through a channel includes a processor circuit, a network interface in communication with the processor circuit, and a computer readable medium in communication with the processor circuit and encoded with codes for directing the processor circuit to: receive from the mobile telephone an access code request message including a callee identifier associated with the callee; communicate with the routing controller to obtain from the routing controller an access code identifying the channel, the access code being different from the callee identifier and useable by the mobile telephone to initiate a call to the callee using the channel; and cause an access code reply message including the access code to be transmitted to the mobile telephone.
- the network interface may include a non-voice network interface
- the codes for directing the processor circuit to receive may include codes for directing the processor circuit to cause the access code request message to be received using the non-voice network interface on a non-voice network.
- the computer readable medium may be further encoded with codes for directing the processor circuit to cause the access code to be produced.
- the codes for directing the processor circuit to cause the access code to be produced may cause the access code to be selected from a pool of access codes, where each access code in the pool of access codes identifies a respective telephone number.
- the computer readable medium may be further encoded with codes for directing the processor circuit to cause to be determined a local calling area associated with the mobile telephone.
- the codes for directing the processor circuit to cause to be determined may cause a dialing profile associated with the caller to be accessed, the dialing profile including a location field having contents identifying at least a default location of the caller.
- the codes for directing the processor circuit to cause to be determined may cause to be received an IP address of the mobile telephone in a wireless IP network.
- the codes for directing the processor circuit to cause to be determined may cause to be received an identifier of a wireless voice signal station in wireless communication with the mobile telephone.
- the codes for directing the processor circuit to cause to be determined may cause to be received a user-configured identifier of a location associated with the mobile telephone.
- the codes for directing the processor circuit to cause the access code to be produced may further cause to be selected an access code in the local calling area associated with the mobile telephone.
- Each access code in the pool of access codes may further identify a respective channel operably configured to cooperate with an IP network to cause a call involving the mobile telephone and the callee to be routed through the IP network.
- the computer readable medium may be further encoded with codes for directing the processor circuit to cause communication through the IP network to be established in response to a call received on the channel.
- the codes for directing the processor circuit to cause the access code to be produced may cause a caller identifier associated with the mobile telephone to be stored in association with the access code.
- the codes for directing the processor circuit to cause communication to be established may cause communication to be established only if the caller identifier associated with the access code identifies the mobile telephone.
- the codes for directing the processor circuit to cause the access code to be produced may cause the callee identifier to be stored in association with the access code.
- the codes for directing the processor circuit to cause the access code to be produced may cause the pool of access codes to be searched for an access code associated with the callee identifier to identify the channel usable by the mobile telephone to initiate a call to the callee.
- the codes for directing the processor circuit to cause the access code to be produced may cause a timestamp for use in determining when the usability of the access code to initiate a call to the callee will expire, to be stored in association with the access code.
- the codes for directing the processor circuit to cause communication to be established may cause communication to be established only if the usability of the access code to initiate a call to the callee has not expired.
- the network interface may include a non-voice network interface, and the codes for directing the processor circuit to transmit include codes for directing the processor circuit to cause the access code reply message to be transmitted using the non-voice network interface on a non-voice network.
- a computer readable medium encoded with codes for directing a processor circuit to: receive from the mobile telephone an access code request message including a callee identifier associated with the callee; communicate with the routing controller to obtain from the routing controller an access code identifying the channel, the access code being different from the callee identifier and useable by the mobile telephone to initiate a call to the callee using the channel; and cause an access code reply message including the access code to be transmitted to the mobile telephone.
- FIG. 1 is a block diagram of a system for enabling a mobile telephone to initiate a call through a channel to a callee in accordance with a first embodiment in the invention
- FIG. 2 is a block diagram of mobile telephone shown in FIG. 1 ;
- FIG. 3 is a flow chart of a process executed by the mobile telephone shown in FIG. 1 ;
- FIG. 4 is a schematic representation of an access code request message transmitted between the mobile telephone and an access server shown in FIG. 1 ;
- FIG. 5 is a schematic representation of an access code reply message transmitted between the mobile telephone and the access server shown in FIG. 1 ;
- FIG. 6 is a block diagram of the access server shown in FIG. 1 ;
- FIG. 7 is a flow chart of a process executed by the access server shown in FIG. 1 ;
- FIG. 8 is a block diagram of a routing controller shown in FIG. 1 ;
- FIG. 9 is a tabular representation of a dialing profile stored in a database accessible by the routing controller illustrated in FIG. 1 ;
- FIG. 10 is a tabular representation of an access code association table stored in memory accessible by the routing controller shown in FIG. 1 ;
- FIG. 11 is a schematic representation of a DID bank table record stored in a database shown in FIG. 1 ;
- FIG. 12 is a flow chart of a process executed by the routing controller illustrated in FIG. 1 ;
- FIG. 13 is a block diagram of a gateway shown in FIG. 1 ;
- FIG. 14 is a tabular representation of an SIP invite message transmitted between the gateway and a call controller illustrated in FIG. 1 ;
- FIG. 15 is a block diagram of the call controller illustrated in FIG. 1 ;
- FIG. 16 is a flow chart of a process executed by the call controller illustrated in FIG. 1 ;
- FIG. 17 is a tabular representation of an RC request message transmitted between the call controller and the routing controller illustrated in FIG. 1 ;
- FIGS. 18A-18C are a flow chart of a process executed by the routing controller illustrated in FIG. 1 ;
- FIG. 19 is a tabular representation of a gateway node association table stored in the database illustrated in FIG. 1 .
- the system 10 includes a first node 11 , a second node 21 , and a mobile telephone 12 .
- the first and second nodes 11 and 21 in the illustrated embodiment may support “voice-over-IP” (VoIP) calls between telephones and/or videophones using the Internet Protocol (IP), as described in PCT Publication No. WO 2008/052340, which is hereby incorporated by reference in its entirety herein.
- VoIP voice-over-IP
- IP Internet Protocol
- the first node 11 is located in a geographical area, such as Vancouver, British Columbia, Canada, for example
- the second node 21 is located in London, England, for example.
- Different nodes may be located in different geographical regions throughout the world to provide telephone/videophone service to subscribers in respective regions.
- These nodes may be in communication with each other by high speed/high data throughput links including optical fiber, satellite, and/or cable links illustrated generally at 17 , forming a backbone to the system. These nodes may alternatively, or in addition, be in communication with each other through conventional internet services.
- the first node 11 provides telephone/videophone service to western Canadian customers from Vancouver Island to Ontario.
- Another node may be located in Eastern Canada to provide services to subscribers in that area, for example.
- nodes of the type shown may also be employed within the geographical area serviced by a node to provide for call load sharing, for example, within a region of the geographical area serviced by the node. However, in general, all nodes may be similar and have the properties described in connection with the first node 11 .
- the first node 11 includes a call controller (CC) 13 , an access server 14 , a routing controller (RC) 30 , a database 23 , a voicemail server 19 , and a media relay 28 .
- CC call controller
- RC routing controller
- the voicemail server 19 need not be included in the node and can be provided by a third party service provider.
- the access server 14 is illustrated as being part of the first node 11 , access servers in alternative embodiments may be separate from the node and may be in communication with one or more nodes, for example.
- the mobile telephone 12 is configured to place calls over a mobile telephone network, illustrated generally at 15 , in a manner well-known in the art. Furthermore, the mobile telephone 12 and the access server 14 are configured to communicate with each other, preferably on a non-voice network illustrated generally at 16 , such as a “WiFi” wireless IP network or a General Packet Radio Service (GPRS) network, for example. However, in alternative embodiments, the mobile telephone 12 and the access server 14 may communicate with each other over other networks, such as a mobile telephone network using Short Message Service (SMS) messages, for example.
- SMS Short Message Service
- the system 10 further includes a gateway 18 in communication with at least one, and preferably a plurality of, channels, which are illustrated schematically at 20 , 22 , and 24 , to which the mobile telephone 12 may initiate a call over the mobile telephone network 15 .
- the channels 20 , 22 , and 24 maybe telephone lines in a Public Switched Telephone Network (PSTN) 29 .
- PSTN Public Switched Telephone Network
- the channels 20 , 22 , and 24 maybe associated with PSTN telephone numbers in a local calling area associated with the mobile telephone 12 , and thus these channels preferably depend on a geographical location of the mobile telephone.
- the expression “local calling area” herein refers generally to a set of telephone numbers, typically defined by a geographical region, to which telephone calls may be placed by callers within the local calling area at either no additional charge or at a lower additional charge than would be required for calls to numbers that are outside of the local calling area.
- the gateway 18 may be in communication with any number of channels, which need not be PSTN telephone lines.
- the channels 20 , 22 , and 24 are associated with telephone numbers for Vancouver, British Columbia, Canada and the surrounding area, although it will be appreciated that these channels may include PSTN telephone lines associated with other areas, for example, which may not necessarily be in a local calling area associated with the mobile telephone 12 .
- each of the channels 20 , 22 , and 24 is configured by a PSTN service provider (which, in Canada, may be Bell Canada or Telus, for example) to direct calls that are received on the channels to the gateway 18 .
- the PSTN service provider has configured the channels 20 , 22 , and 24 to communicate with a T1 multiplexer 25 , which multiplexes the channels 20 , 22 , and 24 in a manner known in the art onto one or more T1 lines 27 that are in communication with the gateway 18 .
- the gateway 18 is in communication with an IP network shown generally at 26 .
- the channels 20 , 22 , and 24 are thus configured to cooperate with the IP network 26 (via the gateway 18 in the illustrated embodiment) to cause a call involving the mobile telephone 12 and the callee to be routed through the IP network in response to a call received at one of the channels.
- the access server 14 is in communication with the routing controller 30 of the first node 11 , and the routing controller 30 is configurable to associate a callee identifier with one of the channels 20 , 22 , and 24 , as described below.
- a callee identifier associated with one of the channels 20 , 22 , and 24 may be a telephone number of a PSTN telephone 32 that is in communication with the IP network 26 through a gateway 34 , or it may be a telephone number of a VoIP telephone 36 that is directly in communication with the IP network 26 , for example.
- Other routing controllers 30 of other nodes, such as the second node 21 may also associate callee identifiers with other channels that are in communication with other gateways (not shown).
- the mobile telephone ( 12 ) includes a processor circuit shown generally at 50 .
- the processor circuit 50 includes a microprocessor 52 , a program memory 54 , an input/output (I/O) port 56 , parameter memory 58 , and temporary memory 60 .
- the program memory 54 , I/O port 56 , parameter memory 58 , and temporary memory 60 are all in communication with the microprocessor 52 .
- the processor circuit 50 may alternatively include a plurality of processors, a plurality of program memories, a plurality of temporary memories, and/or a plurality of I/O ports, or these components may alternatively be combined into a single device. However, for simplicity, the components of the processor circuit 50 are illustrated as shown in the example of FIG. 2 .
- the I/O port 56 includes a dialing input 62 for receiving a callee identifier from a key pad, for example, or from a voice recognition unit, or from pre-stored callee identifiers stored in the parameter memory 58 , for example.
- a dialing input 62 for receiving a callee identifier from a key pad, for example, or from a voice recognition unit, or from pre-stored callee identifiers stored in the parameter memory 58 , for example.
- a myriad of possible dialing functions for providing a callee identifier are represented by the block entitled dialing function 64 .
- a callee identifier may be a telephone number of a callee, for example.
- the I/O port 56 also includes a handset interface 66 for receiving and producing signals to and from a handset 68 that may be placed close to the user's ear and mouth, for producing and receiving audible signals for and from the user.
- the handset 68 may include a camera and video screen, for example, and that video or other types of signals may be transmitted additionally or alternatively to audible signals.
- the I/O port 56 also includes a non-voice network interface 70 for transmitting information to, and receiving information from, the non-voice network 16 illustrated in FIG. 1 , for example, and preferably interfaces with a high-speed internet connection.
- the I/O port 56 in the illustrated embodiment further includes a mobile telephone network interface 72 for transmitting signals to and receiving signals from a mobile telephone service provider over a network such as a Global System for Mobile communications (GSM) or a Code Division Multiple Access (CDMA) network, such as the mobile telephone network 15 illustrated in FIG. 1 , for example.
- a mobile telephone network interface is illustrated, although it will be appreciated that video signals or other signals may be handled similarly when the mobile telephone ( 12 ) is facilitating communication of one or more of these types of signals.
- the non-voice network interface 70 and mobile telephone network interface 72 need not be distinct, but may be a single interface for communication over a single network, for example, or may be configured to communicate over a plurality of different networks, for example.
- the parameter memory 58 includes a username field 74 and a password field 76 , although it will be appreciated that the username and password may not be necessary, or may be input by the user as required, for example.
- the parameter memory 58 in the illustrated embodiment also includes a caller identifier field 78 for storing a caller identifier, which may be a telephone number associated with the mobile telephone ( 12 ) for identifying a “channel” such as a telephone line assigned to the mobile telephone that may be used to call back to the mobile telephone, for example.
- a caller identifier which may be a telephone number associated with the mobile telephone ( 12 ) for identifying a “channel” such as a telephone line assigned to the mobile telephone that may be used to call back to the mobile telephone, for example.
- the contents of the username field 74 , the password field 76 , and the caller identifier field 78 are set once when the user first subscribes to the system.
- the usernames referred to herein such as the username in the username field 74 , preferably include a twelve digit number such as 2001 1050 8667, for example, wherein the left-most digit is a continent code (such as “2” to indicate North America, for example), followed by a three-digit country code (such as “001” to indicate Canada and the United States, for example), a four-digit dealer code (such as “1050”, for example), and a unique four-digit number code (such as “8667”, for example), as discussed more generally in PCT Publication No. 2008/052340. Therefore, a prefix of a username referred to herein preferably indicates a geographical region associated with the user, or with the access code, and more preferably indicates a node associated with the user or access code.
- the program memory 54 stores blocks of codes for directing the microprocessor 52 to carry out the functions of the mobile telephone ( 12 ), which are illustrated by example below.
- FIGS. 2 and 3 a flow chart representing functions performed by blocks of code that direct the microprocessor 52 to initiate a call with the mobile telephone 12 to a callee is shown generally at 100 .
- the blocks shown in FIG. 3 generally represent codes that may be stored in the program memory 54 for example, for directing the microprocessor 52 to perform various functions relating to initiating a call with the mobile telephone ( 12 ) to a callee.
- the actual code to implement each block may be written in any suitable programming language, such as Java, C, and/or C++, for example.
- the process 100 begins at 102 , in response to an interrupt produced at or for the microprocessor 52 by the dialing function 64 .
- block 104 directs the microprocessor 52 to obtain a callee identifier from the dialing function 64 at the dialing input 62 of the I/O port 56 in the illustrated embodiment.
- the callee identifier is associated with a desired callee, and may be a telephone number of the callee, for example.
- the microprocessor 52 thus receives, from a user of the mobile telephone ( 12 ), a callee identifier associated with a callee.
- Block 106 directs the microprocessor 52 to transmit, using the non-voice network interface 70 in the illustrated embodiment, an access code request message, the access code request message including the callee identifier obtained at block 104 , to the access server 14 (illustrated in FIG. 1 ).
- block 106 directs the microprocessor 52 to cause an access code request message to be transmitted to the access server 14 over a non-voice network, such as an internet, using WiFi or GPRS technology for example.
- block 106 may direct the microprocessor 52 to transmit an access code request message to the access server 14 using any suitable technique, which may alternatively include a voice network, for example.
- the access code request message 110 includes a username field 112 , a password field 114 , a callee identifier field 116 , and a caller identifier field 118 .
- values for the username, password, and caller identifier fields 112 , 114 , and 118 are retrieved from the username, password, and caller identifier fields 74 , 76 , and 78 respectively in the parameter memory 58 of the processor circuit 50 (illustrated in FIG.
- a value for the callee identifier field 116 is obtained from the dialing function 64 in block 104 , and may be stored in the temporary memory ( 60 ), for example.
- the username field 112 , password field 114 , and caller identifier field 118 are not essential, although these fields are preferable in order to identify the user of the mobile telephone for billing purposes, for example.
- the channels 20 , 22 , 24 will preferably be local or relatively inexpensive telephone lines associated with a geographical location, more particularly a pre-defined local calling area, associated with the mobile telephone 12 . Therefore, the exemplary access code request message 110 further includes a location identifier field 119 .
- the location identifier stored in the location identifier field 119 preferably identifies a location of the mobile telephone 12 for use in determining a local calling area associated with the mobile telephone 12 .
- the location identifier in the location identifier field 119 may include an IP address of the mobile telephone 12 in a wireless IP network, such as the non-voice network 16 to which the non-voice network interface 70 shown in FIG. 2 is connected, because this IP address may be an indicator of a geographical location of the mobile telephone 12 .
- the location identifier may also or alternatively include an identifier of a wireless voice signal station in wireless communication with the mobile telephone.
- the wireless voice signal station is part of the mobile telephone network 15 that is in communication with the mobile telephone 12 through the mobile telephone network interface 72 illustrated in FIG. 2 .
- the location identifier may include a user-configured identifier of a geographical location or local calling area where the mobile telephone 12 is or may be situated.
- the location identifier may thus be pre-determined and stored in the parameter memory 58 shown in FIG. 2 or may be acquired from non-voice network or wireless voice signal station or from user input, for example. Therefore, in summary, the location identifier in the location identifier field 119 may include one or more of an IP address of the mobile telephone 12 in a wireless IP network, an identifier of a wireless voice signal station in wireless communication with the mobile telephone, and a user-configured identifier.
- the location identifier in the location identifier field 119 may be used to determine a local calling area associated with the mobile telephone 12 , within which local calling area channels (illustrated as 20 , 22 , and 24 in FIG. 1 ) are available to the mobile telephone 12 for the lowest cost to the user.
- the location identifier may only approximately identify a local calling area, and may not necessarily identify the lowest cost channel (illustrated as 20 , 22 , and 24 in FIG. 1 ) for the mobile telephone 12 .
- the location identifier field 119 may be omitted.
- the process 100 continues at block 130 , which directs the microprocessor ( 52 ) to receive an access code reply message from the access server ( 14 ) in response to the access code request message that was transmitted at block 106 .
- the access code reply message 140 includes an access code field 142 and a timeout field 144 .
- the access code field 142 stores an access code which is a telephone number associated with a telephone line associated with one of the channels 20 , 22 , or 24 in FIG. 1 .
- the access code is different from the callee identifier in the callee identifier field 116 shown in FIG. 4 , in that the access code identifies a channel, other than that provided by the callee identifier provided by the dialing function 64 in FIG. 2 , that the mobile telephone ( 12 ) can use to initiate a call to the callee.
- use of the access code facilitates avoidance of long distance or roaming charges that a mobile telephone service provider would charge for a call placed directly using the callee identifier using conventional calling processes, for example.
- the timeout field 144 in the illustrated embodiment stores a value that indicates a period of time, for example a number of minutes, during which the access code in the access code field 142 is associated with the callee identifier in the callee identifier field 116 of the exemplary access code request message 110 illustrated in FIG. 4 , such that the access code is only temporarily associated with the callee identifier.
- the value stored in the timeout field 144 indicates 10 minutes, for example. It will be appreciated that in other embodiments, the timeout field 144 may not be necessary, but preferably it is included.
- the program codes in block 130 direct the microprocessor 52 to receive the access code reply message over a non-voice network, such as a WiFi or GPRS network (illustrated at 16 in FIG. 1 ) via the non-voice network interface 70 shown in FIG. 2 .
- a non-voice network such as a WiFi or GPRS network (illustrated at 16 in FIG. 1 ) via the non-voice network interface 70 shown in FIG. 2 .
- the access code reply message may be received on any suitable network, even a voice network, for example.
- block 149 directs the microprocessor 52 to initiate a call with the mobile telephone ( 12 ) on the mobile telephone network 15 (illustrated in FIG. 1 ) using the access code received in the access code field 142 of the access code reply message 140 (shown in FIG. 5 ) to identify the callee.
- the codes in block 149 direct the microprocessor 52 to initiate a call to the channel ( 20 , 22 , or 24 ) identified by the access code, using the mobile telephone network interface 72 of the I/O port 56 of the mobile telephone ( 12 ), to engage the mobile telephone network ( 15 ).
- the access code in the access code field ( 142 ) is a telephone number identifying a channel 20 , 22 , or 24 that is in communication with the gateway 18 to the IP network 26 .
- the channel 20 , 22 , or 24 is thus operably configured to cooperate with the IP network 26 to cause a call from the mobile telephone 12 to the callee to be routed through the IP network. Routing the call through the IP network may involve engaging the routing controller 30 to route the call on the IP network 26 to the callee, as described below.
- the access code need not be a telephone number, but may be any code identifying a channel through which the mobile telephone 12 can initiate a call.
- the access code may be used to identify an IP address in the IP network to which the call is routed.
- the IP address may act as the access code.
- the access server ( 14 ) includes a processor circuit shown generally at 150 .
- the processor circuit 150 includes a microprocessor 152 , program memory 154 , an I/O port 156 , parameter memory 158 , and temporary memory 160 .
- the program memory 154 , I/O port 156 , parameter memory 158 , and temporary memory 160 are all in communication with the microprocessor 152 .
- the processor circuit 150 may alternatively include a plurality of microprocessors or I/O ports, for example, and the components of the illustrated processor circuit 150 may also alternatively be combined into a single device.
- the program memory 154 stores blocks of codes for directing the microprocessor 152 to carry out the functions of the access server 14 .
- the I/O port 156 includes a non-voice network interface 162 for communicating with the non-voice network 16 illustrated in FIG. 1 .
- the I/O port 156 also includes a routing controller interface 164 for interfacing with the routing controller 30 illustrated in FIG. 1 .
- FIGS. 6 and 7 a flow chart of blocks of code for directing the microprocessor 152 of the access server ( 14 ) to provide an access code to the mobile telephone ( 12 ) is shown generally at 190 .
- the blocks 190 in FIG. 7 generally represent codes that may be stored in the program memory 154 for directing the microprocessor 152 to perform various functions to provide the access to the mobile telephone ( 12 ) to enable the mobile telephone to place a call through a channel ( 20 , 22 , or 24 ).
- the process 190 begins at 192 , in response to an interrupt created by or for the microprocessor 152 when it receives an access code request message 110 (as illustrated in FIG. 4 ) from the mobile telephone ( 12 ).
- the access code request message ( 110 ) is received via the non-voice network interface 162 through a non-voice network ( 16 ) such as a WiFi or GPRS network, for example.
- a non-voice network such as a WiFi or GPRS network
- block 196 which directs the microprocessor 152 to communicate with the routing controller 30 to obtain from the routing controller an access code identifying a channel (illustrated as 20 , 22 , or 24 in FIG. 1 ) in communication with the gateway ( 18 ), wherein the access code is different from the callee identifier in the callee identifier field 116 (shown in FIG. 4 ) and is usable by the mobile telephone ( 12 ) to initiate a call to the callee using the channel, as further described below. Therefore, block 196 preferably causes an access code to be produced by retransmitting the access code request message 110 illustrated in FIG. 4 that was received at 192 from the mobile telephone ( 12 ), to the routing controller 30 through the routing controller interface 164 of the I/O port 156 .
- the process 190 continues at block 198 , which directs the microprocessor 152 to transmit an access code reply message ( 140 ), including the access code obtained by block 196 , to the mobile telephone ( 12 ).
- An exemplary access code reply message is shown in FIG. 5 .
- an access code reply message ( 140 ) is produced by the routing controller 30 in a manner described below in response to the access code request message ( 110 ) that was transmitted to the routing controller at block 196 , and the access code reply message ( 140 ) is received from the routing controller through the routing controller interface 164 of the I/O port 156 .
- Block 198 then causes the access code reply message that was received from the routing controller to be retransmitted to the mobile telephone ( 12 ).
- the codes in block 198 direct the microprocessor 152 to transmit the access code reply message ( 140 ) using the non-voice network interface 162 to the non-voice network 16 , which may be a WiFi or GPRS network, for example.
- the non-voice network 16 which may be a WiFi or GPRS network, for example.
- the process 190 is then ended.
- the access server 14 generally acts as an interface to the routing controller 30 for relaying access code request messages and access code reply messages between the mobile telephone 12 and the routing controller. Therefore, it will be appreciated that in alternative embodiments, the access server 14 and the routing controller 30 need not be separate, but may, for example, be combined in a single component.
- the routing controller 30 executes a process to facilitate communication between callers and callees.
- the function of a routing controller generally in a VoIP system is described in PCT Publication No. WO 2008/052340.
- the routing controller ( 30 ) includes a processor circuit shown generally at 230 .
- the processor circuit 230 includes a microprocessor (or more generally a processor) 232 , program memory 234 , an I/O port 236 , table memory 238 , temporary memory 240 , and a clock 244 .
- the program memory 234 , I/O port 236 , table memory 238 , temporary memory 240 , and clock 244 are all in communication with the processor 232 .
- the processor circuit 230 may include a plurality of microprocessors, for example, and the aforementioned components of the processor circuit 230 may be combined, for example.
- the program memory 234 includes blocks of code for directing the processor 232 to carry out the functions of the routing controller ( 30 ), and the I/O port 236 includes an access server interface 242 for communicating with the access server 14 .
- the access server ( 14 ) transmits (at block 196 illustrated in FIG. 7 ) an access code request message ( 110 ) to the routing controller ( 30 ) in order to obtain from the routing controller ( 30 ) an access code.
- the processor 232 preferably stores certain values from the access code request message in stores in the temporary memory 240 for ease of retrieval.
- the temporary memory 240 includes a callee identifier store 246 for storing the callee identifier from the callee identifier field 116 in the access code request message 110 illustrated in FIG.
- the temporary memory 240 also includes a local calling area identifier store 245 for storing an identifier of a local calling area associated with the mobile telephone ( 12 ).
- the clock 244 generally maintains and stores a representation of a current date and time.
- the I/O port 236 further includes a database request port 256 through which a request to the database ( 23 in FIG. 1 ) can be made, and also includes a database response port 258 for receiving a reply from the database ( 23 ).
- the I/O port 236 further includes a routing controller (RC) request message input 260 for receiving an RC request message (illustrated in FIG. 17 ) from the call controller ( 13 in FIG. 1 ) and includes a routing message output 262 for sending a routing message back to the call controller 13 .
- RC routing controller
- the I/O port 236 thus acts to receive a caller identifier and a callee identifier contained in an RC request message from the call controller, the RC request message being received in response to initiation of a call by a subscriber of the system, as described below.
- the program memory 234 includes blocks of codes for directing the processor 232 to carry out various functions of the routing controller ( 30 ).
- One of these blocks includes an RC request message handler 380 which directs the routing controller ( 30 ) to produce a routing message in response to a received RC request message, an example of which is illustrated in FIG. 17 .
- the RC request message handler process is shown in greater detail at 380 in FIGS. 18A through 18C .
- Another of these blocks in the program memory 234 includes an access code generator, which is described at 270 in FIG. 12 , and which directs the routing controller ( 30 ) to produce an access code as directed by the program codes in block 196 shown in FIG. 7 .
- Yet another of these blocks in the program memory 234 includes a local calling area identifier generator, which directs the routing controller ( 30 ) to produce a local calling area identifier using the location identifier from the location identifier field 119 of the access code request message 110 illustrated in FIG. 4 .
- blocks in the program memory 234 include a local calling area identifier generator, which directs the routing controller 30 to produce a local calling area identifier.
- the local calling area identifier generator may direct the microprocessor 152 to access a dialing profile associated with the caller.
- the dialing profile may be identified using the username in the username field 112 in the access code request message 110 illustrated in FIG. 4 , and to store in the local calling area identifier field 245 a default location of the caller retrieved from the dialing profile associated with the caller.
- an exemplary dialing profile is illustrated generally at 200 and includes a username field 202 , a domain field 204 , and calling attributes comprising a national dialing digits (NDD) field 206 , an international dialing digits (IDD) field 208 , a country code field 210 , a local area codes field 212 , a caller minimum local number length field 214 , a caller maximum local number length field 216 , a reseller field 218 , a maximum number of concurrent calls field 220 , a current number of concurrent calls field 222 , and a default local calling area identifier field 224 .
- NDD national dialing digits
- IDDD international dialing digits
- the local calling area identifier generator directs the microprocessor 152 to determine a local calling area associated with the mobile telephone ( 12 ) by retrieving the default local calling area identifier from the default local calling area identifier field 224 of the dialing profile 200 .
- the dialing profile 200 is a record identifying calling attributes of the caller identified by the username in the username field 202 . More generally, dialing profiles 200 represent calling attributes of respective users, and are discussed in more detail in PCT publication No. WO 2008/052340. As described in PCT publication No. WO 2008/052340, a dialing profile of the type shown in FIG. 9 , and also other records such as direct-in-dial (DID) records, call blocking records, call forwarding records, and voicemail records, may be created whenever a user registers with the system or agrees to become a subscriber to the system.
- DID direct-in-dial
- the local calling area identifier generator may generate a local calling area identifier to be stored in the local calling area identifier store 245 using the location identifier from the location identifier field 119 of the access code request message 110 illustrated in FIG. 4 .
- the location identifier field ( 119 ) may store one or more of an IP address of the mobile telephone ( 12 ) in a wireless IP network, an identifier of a wireless voice signal station in wireless communication with the mobile telephone, and a user-configured identifier. One or more of these values may be used to identify a local calling area that is or is likely to be associated with the mobile telephone ( 12 ) in order to generate a local calling area identifier to be stored in the local calling area identifier store 245 .
- a local calling area may be identified by hierarchical jurisdictional designations (such as country, province, and city in Canada or country, state, and city in the United States) and encoded as codes identifying the local calling area. These codes may then be stored in the local calling area identifier store 245 .
- the table memory 238 (shown in FIG. 8 ) includes an access code association table 170 , an example of which is illustrated in FIG. 10 , for associating access codes with callee identifiers, caller identifiers, caller usernames, timeouts, and timestamps.
- the routing controller ( 30 ) is illustrated in this embodiment as a separate component from the access server ( 14 ), it will be appreciated that in other embodiments, the routing controller ( 30 ) may be part of or integrated with the access server ( 14 ), and in these other embodiments, the access code association table 170 may be part of or integrated with the access server.
- the access code association table 170 generally includes a plurality of records, each having an access code field 173 storing an access code.
- the access codes in the access code association table 170 may thus form a pool of access codes, where each access code may identify a respective telephone number.
- the access codes in the access code fields 173 of records of the access code association table 170 identify respective channels (illustrated by example only as 20 , 22 , and 24 ) that are operably configured to cooperate with the IP network 26 via the gateway 18 to cause a call involving the mobile telephone 12 to be routed through the IP network.
- the exemplary access code association table 170 includes records 172 , 174 , 176 , 178 , and 180 , each having respective fields for storing a local calling area identifier 171 , an access code 173 , a channel identifier 175 , a callee identifier 177 , a caller identifier 179 , a caller username 183 , a timeout 181 , and a timestamp 182 .
- a record in the access code association table 170 will be created for each access code that identifies a channel (such as the channels 20 , 22 , and 24 illustrated in FIG.
- the local calling area identifier field 171 is preferably initialized with an identifier of a local calling area associated with the channel
- the access code field 173 is preferably initialized with an access code associated with the channel
- the channel identifier field 175 is preferably initialized with an identifier of the channel.
- the remaining fields are preferably initialized with default “null” values when a record is created.
- the fields for storing a local calling area identifier 171 , an access code 173 , a channel identifier 175 preferably remain generally constant during ordinary operation of the access code association table 170 , although the values stored in the fields for storing a callee identifier 177 , a caller identifier 179 , a caller username 183 , a timeout 181 , and a timestamp 182 may vary as described below.
- one or more of the fields for storing a local calling area identifier 171 , a channel identifier 175 , a caller identifier 179 , a caller username 183 , a timeout 181 , and a timestamp 182 may not be required and be omitted.
- the local calling area identifier field 171 is preferably initialized with an identifier of a local calling area associated with the channel.
- the local calling area identifier field 171 preferably stores codes that are encoded in the same manner as the codes in the local calling area identifier store 245 , as described above, so that an access code in the local calling area identified by the codes in the local calling area identifier store 245 may be identified by searching the access code association table 170 for an access code associated with a local calling area identifier in the associated local calling area identifier field 171 that matches the local calling area identifier in the local calling area identifier store 245 .
- the access codes in the access code fields 173 are telephone numbers for PSTN lines, three of which are in the 604 area code in Vancouver, British Columbia, Canada, and two of which are in the 416 area code in Toronto, Ontario, Canada. It will be appreciated that the access code association table 170 is an example only, and other access code association tables may include any number of access codes, which need not be PSTN telephone numbers, and which need not be limited to particular geographical areas.
- the access code field 173 in the record 174 stores an access code 1-604-345-2323, which may be a local telephone number for Vancouver, British Columbia, Canada
- the callee identifier field 177 of the record 174 stores a callee identifier 1-403-789-1234, which may be a telephone number for a callee in Calgary, Alberta, Canada for example, thereby associating the callee identifier 1-403-789-1234 with the access code 1-604-345-2323.
- the caller identifier field 179 of the record 174 stores a caller identifier 1-416-444-1441 and the caller username field 183 stores a caller username 2001 1050 8667, thereby associating the caller identifier 1-416-444-1441 and caller username 2001 1050 8667 with the aforementioned access code and callee identifier.
- the caller identifier 1-416-444-1441 may be associated with a mobile telephone normally geographically located in Toronto, Ontario, Canada, but which may be in Vancouver and is therefore using a Vancouver-based access code to place a call to a Calgary-based number, for example.
- the timestamp field 182 indicates that the callee identifier 1-403-789-1234, the caller identifier 1-416-444-1441, and the caller username 2001 1050 8667 were associated with the access code 1-604-345-2323 on Jun. 15, 2008 at 10:31 am, and the timeout field 181 indicates that this association is to expire 10 minutes after the time indicated in the timestamp field.
- the exemplary record 178 indicates that the callee identifier 1-604-321-1234, the caller identifier 1-416-444-1234, and the caller username 2001 1050 4141 were associated with the access code 1-416-234-4646 on Jun. 15, 2008 at 2:21 pm, and the timeout field 181 of the record 178 indicates that this association is to expire within 10 minutes of the time in the timestamp field 182 .
- the access code association table 170 may, in other embodiments, be substituted with other data structures or storage media.
- a DID record of the type shown at 370 in FIG. 11 may associate an access code with a callee identifier and with other information such as a caller identifier, a timeout value, and a timestamp value, additionally or alternatively to the access code association table 170 .
- a DID bank table record may be created and stored in a DID bank table in the database ( 23 in FIG. 1 ) when a user registers with the system, to associate the username of the user and a host name of the node with which the user is associated, with a number on the PSTN network formatted in compliance with the E. 164 standard set by the International Telecommunication Union (ITU).
- DID records may, in some embodiments, also associate usernames and host names with respective access codes, and may also associate access codes with respective callee identifiers and with other information such as caller identifiers, timeout values, and timestamp values.
- an exemplary DID bank table record is shown generally at 370 , and includes a username field 371 , a user domain field 372 , and a DID field 373 .
- the username field 371 may store a username of a user of the system, in which case the user domain field 372 stores a host name of the node with which the user is associated, and the DID field 373 stores an E.164 number on the PSTN network associated with the user.
- Exemplary host names stored in the user domain field 372 include sp.yvr.digifonica.com for Vancouver, British Columbia, Canada and sp.lhr.digifonica.com for London England, for example, as described in PCT Publication No. 2008/052340. If the user has multiple telephone numbers, then multiple records of the type shown at 370 would be included in the DID bank table, each having the same username and user domain, but different DID field 373 contents reflecting the different telephone numbers associated with that user.
- DID fields 373 of DID bank table records 370 may also store access codes, in which case the username field 371 may store a username associated with the access code.
- the user domain field 372 stores a host name of the node with which the access code is associated. Therefore, DID bank table records 370 may, in some embodiments, associate usernames and host names with respective access codes.
- the exemplary DID bank table record 370 further includes a callee identifier field 374 , a caller identifier field 375 , a timeout field 376 , a timestamp field 377 , a local calling area identifier field 378 , a channel identifier field 379 , and a caller username field 381 , which may be used in an analogous manner to the callee identifier field 177 , the caller identifier field 179 , the timeout field 181 , the timestamp field 182 , the local calling area identifier field 171 , the channel identifier field 175 , and the caller username field 183 respectively of the access code association table 170 illustrated in FIG. 10 .
- the DID bank table records 370 may thus associate access codes with respective local calling area identifiers, callee identifiers, caller identifiers, caller usernames, timeouts, and timestamps, although the caller identifier field 375 , timeout field 376 , timestamp field 377 , local calling area identifier field 378 , channel identifier field 379 , and caller username field 381 may not be necessary, and one or more of these fields may be omitted in some embodiments.
- callee identifier field 374 may be omitted for DID table records that are not in respect of access codes, but rather are in respect of telephone numbers of users of the system, for example, as described in PCT Publication No. 2008/052340.
- the callee identifier field 374 , caller identifier field 375 , timeout field 376 , and timestamp field 377 of the DID bank table record 370 may also be omitted in embodiments where the access code association table 170 includes records with these types of fields.
- an access code association table 170 associates access codes with respective callee identifiers, caller identifiers, timeout values, and timestamp values.
- the processes described herein for records in the access code association table 170 may additionally or alternatively be applied to DID bank table records 370 in an analogous manner.
- the access server 14 transmits (at block 196 illustrated in FIG. 7 ) an access code request message 110 to the routing controller 30 in order to obtain from the routing controller 30 an access code.
- the processor 232 preferably authenticates the user by making various enquiries of databases to which it has access, to determine whether or not the password in the password field 114 of the access code request message 110 matches a password stored in the database in association with the username in the username field 112 .
- Various functions may be used to pass encryption keys or hash codes back and forth to ensure that the transmittal of passwords is secure. If the user is successfully authenticated, the processor 232 then preferably produces an access code.
- a process for producing an access code is shown generally at 270 .
- the process 270 determines whether the access code in a given record (referred to below as the “currently addressed record”) in the access code association table shown at 170 in FIG. 10 is within the local calling area identified by the local calling area identifier store 245 , and whether the access code is currently available for association with a callee identifier.
- the processor 232 of the routing controller ( 30 ) preferably searches the pool of access codes in the access code association table ( 170 ) to identify an access code identifying a channel usable by the mobile telephone ( 12 ) to initiate a call to the callee, using the process 270 until an available access code in the local calling area identified by the local calling area identifier store 245 is identified.
- the access code generator thus preferably selects an access code from the pool of access codes in the access code association table ( 170 ), and preferably selects an access code in a local calling area associated with the mobile telephone ( 12 ).
- the process 270 begins at block 272 , which directs the processor 232 of the routing controller ( 30 ) to determine whether the access code in the currently addressed record of the access code association table 170 is associated with the same local calling area as the mobile telephone ( 12 ) as identified by the contents of the local calling area identifier store 245 . If at block 272 the access code of the currently addressed record is not associated with the same local calling area as the mobile telephone ( 12 ), the process 270 ends, the next record in the access code association table 170 is addressed, and the process is repeated for the next record in the access code association table.
- the process 270 continues at block 274 , which directs the processor 232 to determine whether the access code of the currently addressed record is associated with a callee identifier. To do this, the processor 232 determines whether the callee identifier field ( 177 ) of the currently addressed record stores a “null” value that was assigned to it on initialization, or whether the callee identifier field instead stores a callee identifier. In other words the processor checks to see whether the currently addressed record has already been in use.
- the callee identifier field ( 177 ) of the currently addressed record in the access code association table ( 170 ) does store a callee identifier and not the “null” value that was assigned to the callee identifier field on initialization (for example, records 174 and 178 in FIG. 10 ), then the access code of that record is associated with a callee identifier, and the process 270 continues at block 278 , which directs the processor 232 to determine whether the association of the callee identifier with the access code has expired.
- the codes at block 278 direct the processor 232 to determine whether the sum of the contents of the timestamp field ( 182 ) and of the timeout field ( 181 ) in the currently addressed record of the access code association table 170 (shown in FIG. 10 ) is less than the current time represented by the clock 244 . If at block 278 the sum of the timeout and timestamp fields in the currently addressed record of the access code association table 170 is less than the time represented by the clock 244 , then the association of the callee identifier with the access code is not expired and the process 270 ends, the next record in the access code association table ( 170 ) is addressed, and the process 270 is repeated for the next record in the access code association table.
- the callee identifier field in the currently addressed record does not store a callee identifier but stores instead the “null” value that was assigned to the callee identifier field on initialization (for example, records 172 , 176 , and 180 ), then the access code of that record is not associated with a callee identifier, and the process 270 continues at block 276 , which directs the processor 232 to store the access code from the access code field 173 of the currently addressed record, in the access code store 250 in the temporary memory 240 .
- the process 270 continues at block 280 , which directs the processor 232 to store the callee identifier from the callee identifier store 246 in the callee identifier field 177 of the currently addressed record, thereby creating an association of the callee identifier with the selected access code.
- the process 270 then continues at block 282 , which directs the processor 232 to store the caller identifier from the caller identifier store 248 (which identifies the mobile telephone 12 shown in FIG. 1 ) in the caller identifier field 179 of the currently addressed record of the access code association table 170 , thereby also storing the caller identifier in association with the selected access code.
- the process 270 then continues at block 283 , which directs the processor 232 to store the caller username from the caller username store 249 in the caller username field 183 of the currently addressed record of the access code association table 170 , thereby also storing the caller username in association with the selected access code.
- the process 270 then continues at block 284 , which directs the processor 232 to store timeout and timestamp values in the timeout and timestamp fields 181 and 182 of the currently addressed record of the access code association table 170 , thus further storing, in association with the selected access code, a timestamp for use in determining when the usability of the access code to initiate a call to the callee will expire.
- a default value such as 10 minutes, for example may be stored in the timeout field 181 of the currently addressed record.
- the current time indicated by the clock 244 is preferably stored in the timestamp field 182 of the currently addressed record.
- the access code association table ( 170 ) might not include fields for a caller identifier, caller username, a timeout, or a timestamp.
- one or more of blocks 282 , 283 , and 284 described above are not necessary, and one or more of the caller identifier store 248 and the caller username store 249 may be omitted.
- the access code generator in the illustrated embodiment responds to receiving an access code request message 110 illustrated in FIG. 4 from the access server ( 14 ) by first authenticating the user, and then by searching through a pool of access codes, using the process 270 shown in FIG. 12 , to identify an access code that is associated with the local calling area identified by the local calling area identifier store ( 245 ) and that is not previously and validly associated with another callee identifier.
- the access code association table ( 170 ) and the process 270 illustrated in FIG. 12 are examples only, and one of ordinary skill in the art will readily appreciate numerous alternative data structures and algorithms.
- the gateway ( 18 ) includes a processor circuit shown generally at 300 , which includes a microprocessor 302 .
- the processor circuit 300 also includes a program memory 304 , a memory 305 , and an I/O port 306 , all of which are in communication with the microprocessor 302 .
- the processor circuit 300 may include multiple processors etc., and the aforementioned components of the processor circuit 300 may alternatively be combined.
- the I/O port 306 includes a channel interface 308 , which, in the illustrated embodiment, is in communication with the channels 20 , 22 , and 24 that were also illustrated in FIG. 1 .
- the channel interface 308 may, for example, be a T1 port for communication with one or more T1 lines (illustrated at 27 in FIG. 1 ) of a PSTN service provider, in a manner well-known in the art.
- the I/O port in the illustrated embodiment also includes an internet interface 309 for interfacing with the Internet Protocol (IP) network 26 illustrated in FIG. 1 .
- IP Internet Protocol
- the program memory 304 stores blocks of codes for directing the microprocessor 302 to carry out the functions of the gateway ( 18 ). It has been found that the AS5350 Universal Gateway available from Cisco Systems, Inc. of San Jose, Calif. may, for example, be suitable as the gateway ( 18 ).
- the microprocessor 302 when a call is received on one of the channels 20 , 22 , or 24 , the microprocessor 302 causes the I/O port 306 to use the internet interface 309 to send a Session Initiation Protocol (SIP) Invite message to a pre-determined node with which the gateway 18 is associated, which in the illustrated embodiment is the first node 11 .
- SIP Session Initiation Protocol
- the gateway 18 will be associated with a node that is geographically closest to the gateway, in order to minimize transmission times over the IP network 26 .
- the call controller 13 In response to the SIP Invite message, the call controller 13 sends an RC request message to the routing controller 30 which makes various enquiries of the database 23 to produce a routing message that is sent back to the call controller 13 .
- the call controller 13 then communicates with the media relay 28 to cause a communications link including an audio path (and a videopath if a videophone call) to be established through the media relay to the same node, a different node, or to a communications supplier gateway as shown generally at 34 to carry audio, and where applicable, video traffic to the call recipient or callee.
- an exemplary SIP Invite message is shown generally at 310 and includes a caller identifier field 312 , a callee identifier field 314 , a digest parameter field 315 , a call identifier field 316 , an IP address field 317 , and a gateway UDP port field 318 .
- Examples of values for the fields in the SIP Invite message 310 are shown for illustration purposes only in FIG. 14 .
- the caller identifier in the caller identifier field 312 is preferably in the form of the telephone number of the caller followed by the “@” symbol, which in turn is followed by the IP address of the gateway ( 18 ) in the IP network ( 26 ).
- the caller identifier may be determined by retrieving calling line identification (CLID) information from the signal provided by the PSTN network ( 29 ) to the gateway ( 18 ) for example. Where the caller identification information is not available to the gateway ( 18 ), the caller identifier in the caller identifier field 312 preferably includes a pre-assigned number (such as 11111 , for example) indicating that the caller identification information was not available, followed by the “@” symbol and then by the IP address of the gateway ( 18 ).
- CLID calling line identification
- the callee identifier in the callee identifier field 314 is the access code identifying the channel ( 20 , 22 , or 24 in the example of FIG. 1 ) on which the call was placed, and which was received from the access server ( 14 ).
- the access code is the PSTN telephone number 1-604-345-1212 corresponding to the channel 20 illustrated in FIG. 1 , and to the access code stored in the access code field 173 of the record 172 in the exemplary access code association table 170 illustrated in FIG. 10 .
- the digest parameter in the digest parameter field 315 is generated by the gateway ( 18 ) and may uniquely identify the SIP session that is initiated with the SIP Invite message 310 .
- the call identifier in the call identifier field 316 is, in the illustrated embodiment, a four-digit hexadecimal number generated by the gateway ( 18 ) to identify the call, followed by the “@” symbol, which in turn is followed by the IP address of the gateway.
- the IP address in the IP address field 317 is the IP address of the gateway ( 18 ) in the IP network ( 26 ), and the gateway UDP port number in the gateway UDP port field 318 includes a UDP port identifier identifying a UDP port at which the audio/video path will be terminated at the gateway ( 18 ).
- the IP/UDP addresses of all elements such as the gateway ( 18 ) will be assumed to be valid IP/UDP addresses directly accessible via the Internet or a private IP network, for example, depending on the specific implementation of the system. As such, it will be assumed, for example, that the gateway ( 18 ) will have an IP/UDP address directly accessible by the call controllers and the media relays on their respective nodes, and those addresses will not be obscured by Network Address Translation (NAT) or similar mechanisms.
- NAT Network Address Translation
- the IP/UDP information contained in SIP messages (for example the SIP Invite message or the RC Request message which will be described below) will match the IP/UDP addresses of the IP packets carrying these SIP messages.
- IP addresses assigned to various elements of the system may be in a private IP address space, and thus not directly accessible from other elements.
- NAT is commonly used to share a “public” IP address between multiple devices, for example between home PCs and IP telephones sharing a single Internet connection.
- the gateway ( 18 ) may be assigned an IP address such as 192.168.0.5. This address is located in so called “non-routable” (IP) address space and cannot be accessed directly from the Internet.
- the IP address has to be converted into a “public” IP address, for example 24.14.102.5 assigned by the Internet Service Provider, by a device performing NAT, typically a router.
- NAT typically also translates UDP port numbers, for example an audio path originating at the gateway ( 18 ) and using a UDP port 12378 at its private IP address, may have be translated to a UDP port 23465 associated with the public IP address of the NAT device.
- the source IP/UDP address contained in the IP packet header will be 24.14.102.5:23465, whereas the source IP/UDP address information contained in the SIP message inside this IP packet will be 192.168.0.5:12378.
- the mismatch in the IP/UDP addresses may cause a problem for SIP-based VoIP systems because, for example, a node will attempt to send messages to a private address but the messages will never get there.
- the call controller ( 13 ) includes a processor circuit shown generally at 320 .
- the processor circuit 320 includes a microprocessor 322 , program memory 324 , and an I/O port 326 .
- the program memory 324 and the I/O port 326 are in communication with the microprocessor 322 .
- the processor circuit 320 may include a plurality of microprocessors, a plurality of program memories, and a plurality of I/O ports to be able to handle a large volume of calls. However, for simplicity, the processor circuit 320 will be described as having only one microprocessor 322 , program memory 324 , and I/O port 326 , it being understood that there may be more.
- the I/O port 326 includes an input 328 for receiving messages such as the SIP Invite message from the gateway ( 18 ) or from a VoIP telephone ( 36 in FIG. 1 , for example).
- the I/O port 326 also has an RC request message output 330 for transmitting an RC request message to the routing controller 30 of FIG. 1 , an RC message input 332 for receiving routing messages from the routing controller 30 , a gateway output 334 for transmitting messages to the gateway 18 and/or 34 shown in FIG. 1 to advise the gateway 18 and/or 34 to establish an audio path, for example, and a gateway input 336 for receiving messages from the gateway 18 and/or 34 .
- the I/O port 326 further includes a SIP output 338 for transmitting messages to the gateway ( 18 and/or 34 ) or VoIP telephone ( 36 , for example) to advise the gateway 18 and/or 34 or IP telephone of the IP addresses of the gateways which will establish the audio/video path.
- the I/O port 326 further includes a voicemail server input and output 340 and 342 respectively for communicating with the voicemail server 19 shown in FIG. 1 .
- the messages sent to the routing controller ( 30 ) and received from the routing controller ( 30 ) may be transmitted and received on the same single IP port.
- the program memory 324 includes blocks of code for directing the microprocessor 322 to carry out various functions of the call controller ( 13 ).
- these blocks of code include a first block 344 for causing the processor circuit 320 to execute a SIP Invite to RC Request process to produce an RC Request Message in response to a received SIP Invite message.
- Block 350 directs the processor circuit 320 to produce an RC Request Message.
- Block 352 then directs the processor circuit 320 to cause the RC Request Message to be sent to the routing controller 30 illustrated in FIG. 1 .
- an exemplary RC request message is shown generally at 360 and includes a caller identifier field 362 , a callee identifier field 364 , a digest parameters field 366 , and a call identifier field 368 . These fields may be populated with the contents of the caller identifier field 312 , callee identifier field 314 , digest parameter field 315 , and call identifier field 316 respectively of the SIP Invite message 310 illustrated in FIG. 14 .
- the RC request message may further include a type field (not shown) containing a type code to indicate whether the call is from a third party or from a system subscriber.
- a type field (not shown) in the RC request message 360 may be advantageous in embodiments where SIP Invite messages may also be received from an IP telephone that is using VoIP software to make a voice call. However, in the embodiments that are illustrated herein, SIP Invite messages originate from the gateway ( 18 ), and therefore a type designation is not necessary and may be omitted from the RC request message 360 . In embodiments where a SIP Invite message may be received from an IP telephone, the SIP invite to RC request process shown in FIG. 16 may require additional steps, as illustrated in FIG. 5 of PCT Publication No. WO 2008/052340.
- the program memory 234 includes an RC request message handler 380 which directs the routing controller ( 30 ) to produce a routing message in response to a received RC request message ( 360 ).
- the RC request message handler 380 begins with a first block 382 that directs the RC processor circuit ( 230 ) to separately store the contents of the callee identifier field 364 and caller identifier field 362 of the RC request message ( 360 ) in the callee identifier store 246 and the caller identifier store 248 respectively of FIG. 8 .
- Block 384 then directs the RC processor circuit ( 230 ) to use the contents of the caller username store 249 to locate and retrieve from the database ( 23 ) a dialing profile 200 associated with the caller, as described above and illustrated in FIG. 9 , for example.
- the retrieved dialing profile may then be stored in the temporary memory 240 , for example.
- the RC request message handler 380 continues at block 386 , which directs the processor circuit ( 230 ) of the routing controller to determine whether the contents of the current number of concurrent calls field 222 of the dialing profile 200 shown in FIG. 9 are less than the contents of the maximum number of concurrent calls field 220 of the dialing profile for the caller and, if so, block 388 directs the processor circuit to increment the contents of the current number of concurrent calls field 222 and the processor circuit ( 230 ) is directed to point A in FIG. 18B .
- block 390 directs the processor circuit ( 230 ) to send an error message back to the call controller ( 13 ) to cause the call controller to notify the caller that the maximum number of concurrent calls has been reached and no further calls can exist concurrently, including the presently requested call.
- the RC processor circuit ( 230 ) is directed to perform certain checks on the callee identifier in the callee identifier field 246 in FIG. 8 . These checks are shown in greater detail in FIG. 18B .
- the RC processor circuit ( 230 ) is directed to a first block 392 that causes it to determine whether a digit pattern of the callee identifier includes a pattern that matches the contents of the international dialing digits (IDD) field 208 in the dialing profile 200 (shown in FIG. 9 ) associated with the caller. If so, then block 394 directs the RC processor circuit ( 230 ) to set a call type code identifier variable maintained by the processor to indicate that the call is an international call, and block 396 directs the processor to produce a reformatted callee identifier by reformatting the callee identifier into a predefined digit format.
- IDD international dialing digits
- block 398 directs the RC processor circuit ( 230 ) to determine whether or not the callee identifier has a length which meets criteria establishing it as a number compliant with the E.164 Standard set by the ITU. If the length does not meet these criteria, then block 400 directs RC processor circuit ( 230 ) to send back to the call controller ( 13 ) a message indicating the length is not correct. The process 380 is then ended.
- routines (not shown) stored in the program memory 324 may direct the processor circuit ( 320 of FIG. 15 ) to respond to the incorrect length message by transmitting a message back to the mobile telephone ( 12 shown in FIG. 1 ) to indicate that an invalid number has been dialed.
- block 402 directs the RC processor circuit ( 230 ) to make a database request to the database ( 23 ) to determine whether or not the amended callee identifier is found in the DID field ( 373 ) of a record such as shown in FIG. 11 in the DID bank table.
- the RC processor circuit ( 230 ) receives a response from the database ( 23 ) indicating that the reformatted callee identifier produced at block 396 is found in the DID field ( 373 ) of a record in the DID bank table, then the callee is a subscriber to the system and the call is classified as a private network call by directing the processor to block 404 , which directs the RC processor circuit ( 230 ) to copy the contents of the corresponding username field ( 371 in FIG. 11 ) from the callee DID bank table record ( 370 in FIG. 11 ) into the callee identifier store ( 246 in FIG. 8 ).
- the RC processor circuit ( 230 ) locates a subscriber username associated with the reformatted callee identifier.
- the processor ( 232 ) is then directed to point B in FIG. 18A .
- the gateway 18 is preferably associated with a pre-determined node, which in the illustrated embodiment is the first node 11 .
- block 406 directs the processor ( 232 of FIG. 8 ) to execute a process to determine whether or not the node associated with the reformatted callee identifier in the callee identifier store ( 246 in FIG. 8 , which, at block 404 , was set to be a username of the callee) is the same node that is associated with the gateway 18 illustrated in FIG. 1 .
- the processor ( 232 ) may, for example, identify a node associated with the gateway ( 18 ) by using an IP address associated with the gateway to determine a node identifier of the gateway.
- An IP address associated with the gateway ( 18 ) may, for example, be obtained from either the caller identifier field 362 or the call identifier field 368 of the RC request message 360 illustrated in FIG. 17 , as each of these fields includes a portion following an “@” symbol that indicates an IP address of the gateway.
- the processor 232 illustrated in FIG. 8
- the exemplary gateway node association table 480 includes first and second records 482 and 484 , each having a respective gateway IP address field 486 and a respective node identifier field 488 . It will be appreciated that the exemplary gateway node association table 480 is an example for illustration purposes only.
- the values in the gateway IP address fields 486 are preferably initialized when a gateway (such as the gateway 18 illustrated in FIG. 1 ) is installed as part of the system ( 10 ), and are preferably updated as the IP addresses of the respective gateways may change from time to time.
- the values in the node identifier fields 488 are also preferably initialized when a gateway (such as the gateway 18 illustrated in FIG. 1 ) is installed as part of the system ( 10 ).
- the reformatted callee identifier in the callee identifier store ( 246 in FIG. 8 ) was set at block 404 in FIG. 18B to be a username of the callee from the username field 371 (illustrated in FIG. 11 ), and in this embodiment, a prefix of the username of the callee preferably indicates a node associated with the callee.
- the left-most digit in the username of the callee is a continent code, which is a sufficient prefix to identify a node associated with the callee.
- other prefixes or other information may identify the associated node.
- the values in the node identifier fields 488 correspond to the prefixes of the usernames in the username fields 371 (illustrated in FIG. 11 ), so that the node associated with the callee is the same node that is associated with the gateway 18 illustrated in FIG. 1 if the prefix of the username of the callee matches the node identifier associated with the gateway ( 18 ). Therefore, in the illustrated embodiment, if the reformatted callee identifier in the callee identifier store ( 246 in FIG. 8 ) is 2001 1050 8667, for example, then in the example of FIG.
- the node associated with the callee is the same node as the node identified by the continent code “2” that is associated with the gateway associated with the IP address 20.14.102.5 in the record 482 , but is not the same node as the node identified by the continent code “5” that is associated with the gateway associated with the IP address 104.12.131.12 in the record 484 .
- block 406 if at block 406 the prefix of the username of the callee does not match the node identifier associated with the gateway ( 18 ), then the call is a “cross-domain” call, and block 408 in FIG. 18A directs the processor ( 232 in FIG. 8 ) to set a call type flag in the temporary memory ( 240 in FIG. 8 ) to indicate the call is a cross-domain call. Then, block 410 of FIG. 18A directs the processor ( 232 of FIG. 8 ) to produce a routing message identifying an address on the private network with which the callee identified by the contents of the callee ID buffer is associated and to set a time to live for the call at a maximum value of 99999, for example.
- Routing messages and time to live values, and also a method of determining the node in the system with which the callee is associated, are further described in PCT Publication No. WO 2008/052340.
- block 412 directs the processor ( 232 in FIG. 8 ) to cause the routing message to be sent to the call controller 13 shown in FIG. 1 , and the process ends.
- block 414 directs the processor ( 232 ) to determine whether or not the callee identifier begins with the same national dial digit code as assigned to the caller. To do this, the processor ( 232 ) is directed to refer to the retrieved caller dialing profile as shown in FIG. 9 . In FIG. 9 , the national dialing digit code 206 is the number 1 . Thus, if the callee identifier begins with the number 1 , then the processor ( 232 ) is directed to block 416 in FIG. 18B .
- Block 416 directs the processor ( 232 of FIG. 8 ) to examine the callee identifier to determine whether or not the digits following the NDD digit identify an area code that is the same as any of the area codes identified in the local area codes field 212 of the caller dialing profile 200 shown in FIG. 9 . If not, block 418 of FIG. 18B directs the processor ( 232 ) to set the call type flag to indicate that the call is a national call. If the digits following the NDD digit identify an area code that is the same as a local area code associated with the caller as indicated by the caller dialing profile, block 420 directs the processor ( 232 ) to set the call type flag to indicate a local call, national style.
- block 422 directs the processor ( 232 ) to format the callee identifier into a pre-defined digit format to produce a re-formatted callee identifier by removing the national dialed digit and prepending a caller country code identified by the country code field 210 of the caller dialing profile shown in FIG. 9 .
- the processor ( 232 ) is then directed to block 398 of FIG. 18B to perform other processing as already described above.
- block 424 directs the processor ( 232 ) to determine whether the callee identifier begins with digits that identify the same area code as the caller. Again, the reference for this is the retrieved caller dialing profile shown in FIG. 9 .
- the processor ( 232 ) determines whether or not the first few digits of the callee identifier identify an area code corresponding to the contents of any area code identifier stored in the local area code field 212 of the retrieved caller dialing profile 200 (illustrated in FIG. 9 ). If so, then block 426 directs the processor ( 232 ) to set the call type flag to indicate that the call is a local call.
- the call will not necessarily be a local call in every case where the first few digits of the callee identifier identify an area code corresponding to the contents of an area code identifier stored in the local area code field 212 (illustrated in FIG. 9 ), and other determinations of when a call is to be considered local may be appropriate. However, it has been found that the determination described above for block 424 is satisfactory for some purposes.
- block 428 directs the processor ( 232 ) to format the callee identifier into a pre-defined digit format to produce a reformatted callee identifier by prepending the caller country code to the callee identifier, the caller country code being determined from the country code field 210 of the retrieved caller dialing profile 200 shown in FIG. 9 .
- the processor ( 232 ) is then directed to block 398 for further processing as described above.
- block 430 directs the processor ( 232 of FIG. 8 ) to determine whether the number of digits in the callee identifier, i.e. the length of the callee identifier, is within the range of digits indicated by the caller minimum local number length field 214 and the caller maximum local number length field 216 of the retrieved caller dialing profile 200 shown in FIG. 9 , and whether there is more than one area code identifier stored in the local area code field 212 of the retrieved caller dialing profile.
- block 432 directs the processor ( 232 ) to set the call type flag to indicate a local call and block 434 directs the processor ( 232 ) to format the callee identifier into a pre-defined digit format to produce a reformatted callee identifier by prepending to the callee identifier the caller country code (as indicated by the country code field 210 of the retrieved caller dialing profile 200 shown in FIG. 9 ) followed by the caller area code as indicated by the local area code stored in the local area code field 212 of the caller dialing profile 200 shown in FIG. 9 .
- the processor ( 232 ) is then directed to block 398 of FIG. 18B for further processing as described above.
- block 430 If at block 430 , the callee identifier has a length that does not fall within the range specified by the caller minimum local number length field ( 214 in FIG. 9 ) and the caller maximum local number length field ( 216 in FIG. 9 ), or if there is more than one area code identifier stored in the local area code field 212 of the retrieved caller dialing profile 200 illustrated in FIG. 9 , then block 436 directs the processor ( 232 ) to send an error message back to the call controller ( 13 ), and the process ends.
- an additional block ( 402 in FIG. 8B of PCT Publication No. WO 2008/052340) may determine whether the callee identifier is a valid username.
- the callee identifier is assumed to be a telephone number of the callee, and not a username.
- blocks 392 , 414 , 424 , and 430 establish call classification criteria for classifying the call as a public network call or a private network call.
- Block 402 classifies the call, depending on whether or not the formatted callee identifier has a DID bank table record, and this depends on how the call classification criteria are met.
- block 438 directs the processor ( 232 ) to determine whether the formatted callee identifier in the callee identifier store 246 in FIG. 8 corresponds to an access code in the access code field 173 of a record in the access code association table 170 illustrated in FIG. 10 that is associated with a callee identifier. Because the callee identifier in the callee identifier store 246 in FIG. 8 has been formatted as described above with reference to FIG. 18B , block 438 may involve determining whether an access code in the access code field 173 of a record of the access code association table 170 (illustrated in FIG.
- block 440 directs the processor ( 232 ) to determine whether the caller identifier in the caller identifier store 248 (illustrated in FIG.
- block 442 directs the processor ( 232 ) to send an error message to the call controller ( 13 ), and the process ends.
- the routing controller ( 30 ) will produce a routing message that will cause the call controller to establish communication through the IP network ( 26 ) to the callee in response to a call received at a channel ( 20 , 22 , or 24 ).
- block 444 includes codes that direct the processor ( 232 ) to determine whether the association of the access code with the callee identifier has expired, and thus whether the usability of the access code to initiate a call to the callee has expired, in the manner described above for block 278 in FIG. 12 . If at block 444 the association of the access code with the callee identifier has expired, then block 442 directs the processor ( 232 ) to send an error message to the call controller ( 13 ), and the process ends. Thus the routing controller produces a routing message that causes the call controller to establish the call only when the association of the access code with the callee identifier has not expired.
- one or more of the caller identifier, timeout, and timestamp fields 179 , 181 , and 182 may be omitted from the access code association table 170 illustrated in FIG. 10 , and in these embodiments, one or more of the blocks 440 , 442 , and 444 may also be omitted.
- block 446 directs the processor ( 232 ) to store the callee identifier from the callee identifier field 177 of the record of the access code association table ( 170 ) in the callee identifier store 246 illustrated in FIG. 8 .
- the processor ( 232 ) is then directed to point A in FIG. 18B to repeat the steps illustrated in FIG. 18B using the callee identifier retrieved from the callee identifier field ( 177 ) in the record of the access code association table ( 170 ).
- block 448 of FIG. 18B causes the processor ( 232 ) to set the contents of the callee identifier store 246 of FIG. 8 to be the newly formatted callee identifier, i.e., a number compatible with the E.164 standard.
- block 450 of FIG. 18B directs the processor ( 232 ) to generate a routing message identifying a gateway to the public network usable by the call controller ( 13 ) to establish a “public system” call.
- block 450 includes codes that, for example, direct the processor ( 232 ) to search a database of route or master list records and to search a database of supplier records to identify at least one supplier operable to supply a communications link for the call, and to load a routing message buffer with supplier information, time to live values, and timeout values.
- An example of an implementation of these steps is described with reference to blocks 410 , 412 , 560 , 562 , 563 , 564 , 566 , and 571 in FIGS. 8B and 8D in PCT Publication No. WO 2008/052340.
- block 452 directs the processor 232 of FIG. 10 to send the routing message to the call controller 13 in FIG. 1 , and the process ends.
- block 454 directs the processor ( 232 ) to use the callee identifier in the callee identifier store 246 illustrated in FIG. 8 (which, at block 404 , was set to be a username of the callee) to locate and retrieve a dialing profile for the callee.
- the dialing profile may be of the type shown in FIG. 9 , for example.
- Block 456 of FIG. 18A then directs the processor 232 of FIG. 8 to get call block, call forward, and voicemail records from the database 23 of FIG. 1 , based on the username identified in the callee dialing profile retrieved by the processor at block 454 . Exemplary call block, call forward, and voicemail records are described in PCT Publication No. WO 2008/052340.
- block 458 directs the processor 232 of FIG. 8 to determine whether or not the caller identifier received in the RC request message matches a block pattern stored in the call block record associated with the callee and retrieved at block 454 . If the caller identifier matches a block pattern, then block 460 directs the processor to send a drop call or non-completion message to the call controller ( 13 ) and the process is ended. If the caller identifier does not match a block pattern associated with the callee, then block 462 directs the processor ( 232 ) to determine whether or not call forwarding is required, as described in PCT Publication No. WO 2008/052340.
- block 464 directs the processor ( 232 ) to generate a routing message identifying an address on the private network, associated with the callee for a “private system” call.
- block 464 includes codes that, for example, direct the processor ( 232 ) to store, in a routing message buffer, a username and domain of the callee, time to live values, and an IP address of the current node, to determine whether or not the user identified by the callee identifier has paid for voicemail service and if so, to store voicemail information in the routing message buffer.
- block 466 directs the processor 232 of FIG. 8 to cause the routing message to be sent to the call controller 13 in FIG. 1 , and the process ends.
- block 468 directs the processor ( 232 ) to search a dialing profile table to find a dialing profile record as shown in FIG. 9 , for the user identified by the destination number field of the call forward record, as illustrated in PCT Publication No. WO 2008/052340.
- the processor ( 232 ) is further directed to store the username and domain for that user and a time to live value in a routing message buffer, an example of which is described in PCT Publication No. WO 2008/052340. This process is repeated for each call forwarding record associated with the callee identified by the callee identifier store 246 in FIG. 8 to add to the routing message buffer all call forwarding usernames and domains associated with the callee.
- the routing message sent at one of blocks 412 , 452 , and 466 is received at the call controller 13 and the call controller interprets the receipt of the routing message as a request to establish a call.
- the program memory 324 of the call controller 13 includes a routing to gateway routine depicted generally at 346 .
- a routing message received at the call controller 13 is of the type produced at block 464 shown in FIG. 18A , indicating that the callee is a system subscriber on the same node as the gateway ( 18 ) (such as a user of the VoIP telephone 36 illustrated in FIG. 1 )
- the routing to gateway routine 346 may direct the microprocessor 322 to cause a message to be sent back through the IP network 26 shown in FIG. 1 to the VoIP telephone ( 36 ), using the IP address of the VoIP telephone ( 36 ) that is available from the callee username.
- the call controller 13 may send a SIP invite message along the high speed/high data throughput link 17 in communication with the other node.
- the other node may function as explained above and in PCT Publication No. WO 2008/052340, in response to receipt of a SIP invite message.
- the call controller 13 If the routing message received at the call controller 13 is of the type produced at block 450 shown in FIG. 18C , indicating that the callee is not a subscriber to the system (such as a user of the PSTN telephone 32 that is in communication with the IP network 26 through the gateway 34 as illustrated in FIG. 1 ), the call controller sends one or more SIP invite messages to the suppliers identified in the routing message to identify the IP address of a supplier that is able to carry the call, such as the IP address of the gateway 34 illustrated in the example of FIG. 1 .
- a process for identifying the IP address of a supplier that is able to carry the call is given in PCT Publication No. WO 2008/052340, which is incorporated herein by reference.
- the gateway of the supplier that is able to carry the call will be the gateway 18 illustrated in FIG. 1 , that is, the same gateway through which the caller telephone ( 12 ) initiated the call.
- the gateways 18 and 34 are distinct gateways. It will be understood that in some cases, they may be the same gateway, but in these cases, the following steps may still be applied.
- the IP address of the gateway 34 is sent in a message from the call controller 13 to the media relay 28 , which responds with a message indicating an IP address to which the gateway 18 should send its audio/video traffic, and an IP address to which the gateway 34 should send its audio/video for the call.
- the call controller conveys the IP address at which the media relay 28 expects to receive audio/video from the gateways 18 and 34 , to the gateways 18 and 34 in one or more messages.
- the gateway 18 replies to the call controller 13 with an IP address at which it would like to receive audio/video, and the call controller conveys that IP address to the media relay 28 .
- the call may then be conducted between the caller and callee through the media relay 28 and the gateways 18 and 34 .
- the call controller 13 receives a routing message of the type produced at block 464 shown in FIG. 18A , indicating that the callee is a system subscriber on the same node as the gateway ( 18 ) (such as a user of the VoIP telephone 36 illustrated in FIG. 1 ), and which has at least one call forwarding number and/or a voicemail number, the call controller attempts to establish a call to the callee VoIP telephone 36 by seeking from the callee telephone a message indicating an IP address to which the media relay 28 should send audio/video. If no such message is received from the callee telephone, no call is established. If no call is established within a pre-determined time, the call controller 13 attempts to establish a call with the next user identified in the call routing message in the same manner.
- the call controller communicates with the voicemail server 19 identified in the routing message to obtain an IP address to which the media relay 28 should send audio/video and the remainder of the process mentioned above for establishing IP addresses at the media relay and the caller telephone is carried out to establish audio/video paths to allowing the caller to leave a voicemail message with the voicemail server.
- a call timer maintained by the call controller 13 preferably logs the start date and time of the call and logs the call ID and an identification of the route (i.e., audio/video path IP address) for later use in billing.
- the gateway 18 sends a SIP bye message to the call controller 13 .
- the gateway 34 or the VoIP telephone 36 of the callee sends a SIP bye message to the call controller 13 .
- Exemplary SIP bye messages are described in PCT Publication No. WO 2008/052340.
- the SIP bye message is received at the call controller 13 , and the call controller executes a process that involves decrementing the contents of the current number of concurrent calls field 222 dialing profile 200 of the caller as illustrated in FIG.
- the routing controller 30 executes an RC call stop message process that involves making various updates to subscriber, reseller, and supplier account records (not shown) following the call. Examples of subscriber, reseller, and supplier account records, and of updates to subscriber, reseller, and supplier account records, are described in PCT Publication No. WO 2008/052340, which is incorporated herein by reference.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
- This application is a continuation of U.S. application Ser. No. 14/035,806, filed Jan. 23, 2014, entitled “Mobile Gateway”, which is a continuation of U.S. application Ser. No. 13/056277, filed Jan. 27, 2011, entitled “Mobile Gateway”, which is a national phase entry of PCT/CA2009/001062, filed Jul. 28, 2009, which claims priority to U.S. Provisional Application No. 61/129,898, filed Jul. 28, 2008, all of which are incorporated by reference in their entireties.
- This invention relates generally to telecommunication, and more particularly to methods, systems, apparatuses, and computer readable media for initiating or enabling a call with a mobile telephone to a callee.
- Mobile telephone service providers often charge significant fees for long distance telephone calls, particularly when the mobile telephone is roaming in another mobile telephone service provider's network.
- One known technique for avoiding the long distance charges of mobile telephone service providers is to use a “calling card”. A “calling card” may permit the user of the mobile telephone to place a call to a local telephone number or to a less-expensive telephone number (such as a toll-free number, for example) instead of placing the call directly to the callee. The user may thus avoid the long distance charges of the mobile telephone service provider, which may be higher than the charges for using the “calling card”. However, this technique can be cumbersome and undesirable, because it may require the user of the mobile telephone to follow a number of complicated or cumbersome steps in order to initiate a call to the callee, for example.
- In accordance with one aspect there is provided a method of initiating a call to a callee using a mobile telephone. The method involves receiving, from a user of the mobile telephone, a callee identifier associated with the callee; transmitting an access code request message to an access server, the access code request message including the callee identifier; receiving an access code reply message from the access server in response to the access code request message, the access code reply message including an access code different from the callee identifier and associated with the callee identifier; and initiating a call with the mobile telephone using the access code to identify the callee.
- Transmitting may involve transmitting the access code request message to the access server on a non-voice network.
- Transmitting may involve transmitting a location identifier of a location associated with the mobile telephone to the access server.
- Transmitting the location identifier may involve transmitting an IP address of the mobile telephone in a wireless IP network.
- Transmitting the location identifier may involve transmitting an identifier of a wireless voice signal station in wireless communication with the mobile telephone.
- Transmitting the location identifier may involve transmitting a user-configured identifier of a location associated with the mobile telephone.
- Receiving the access code reply message may involve receiving the access code reply message from the access server on a non-voice network.
- Receiving the access code reply message may involve receiving, in the access code reply message, an access code temporarily associated with the callee identifier.
- Receiving the access code reply message may involve receiving, in the access code reply message, a telephone number identifying a channel operably configured to cooperate with an IP network to cause a call involving the mobile telephone and the callee to be routed through the IP network.
- Initiating the call may involve engaging a routing controller to route the call on the IP network to the callee.
- The method may further involve: receiving from the mobile telephone the access code request message; communicating with a routing controller to obtain from the routing controller the access code wherein the access code identifies a channel and is useable by the mobile telephone to cause the routing controller to establish a call to the callee using the channel; and transmitting the access code reply message to the mobile telephone.
- In accordance with another aspect, there is provided a mobile telephone. The mobile telephone includes: provisions for receiving, from a user of the mobile telephone, a callee identifier associated with the callee; transmitting provisions for transmitting an access code request message to an access server, the access code request message including the callee identifier; provisions for receiving an access code reply message from the access server in response to the access code request message, the access code reply message including an access code different from the callee identifier and associated with the callee identifier; and provisions for initiating a call using the access code to identify the callee.
- The transmitting provisions may include a non-voice network interface for transmitting the access code request message to the access server on a non-voice network.
- The access code request message may further include a location identifier of a location associated with the mobile telephone.
- The location identifier may include an IP address of the mobile telephone in a wireless IP network.
- The location identifier may include an identifier of a wireless voice signal station in wireless communication with the mobile telephone.
- The location identifier may include a user-configured identifier of a location associated with the mobile telephone.
- The provisions for receiving an access code reply message may include a non-voice network interface for receiving the access code reply message on a non-voice network.
- The access code may include a telephone number.
- The means for initiating may involve a mobile telephone network interface.
- In accordance with another aspect, there is provided a system for initiating a call to a callee. The system includes the mobile telephone, a routing controller, and an access server. The access server includes: provisions for receiving from the mobile telephone the access code request message; provisions for communicating with the routing controller to obtain from the routing controller the access code wherein the access code identifies a channel and is useable by the mobile telephone to cause the routing controller to establish a call to the callee using the channel; and provisions for transmitting the access code reply message including the access code to the mobile telephone.
- In accordance with another aspect, there is provided a mobile telephone. The mobile telephone includes a processor circuit, a network interface in communication with the processor circuit, and a computer readable medium in communication with the processor circuit and encoded with codes for directing the processor circuit to: receive, from a user of the mobile telephone, a callee identifier associated with the callee; cause an access code request message to be transmitted to an access server, the access code request message including the callee identifier; receive an access code reply message from the access server in response to the access code request message, the access code reply message including an access code different from the callee identifier and associated with the callee identifier; and initiate a call using the access code to identify the callee.
- The network interface may include a non-voice network interface, and the codes for directing the processor circuit to cause the access code request message to be transmitted may include codes for directing the processor circuit to cause the access code request message to be transmitted to the access server using the non-voice network interface on a non-voice network.
- The access code request message may further include a location identifier of a location associated with the mobile telephone.
- The location identifier may include an IP address of the mobile telephone in a wireless IP network.
- The location identifier may include an identifier of a wireless voice signal station in wireless communication with the mobile telephone.
- The location identifier may include a user-configured identifier of a location associated with the mobile telephone.
- The network interface may include a non-voice network interface, and the codes for directing the processor circuit to receive an access code reply message may include codes for directing the processor circuit to cause the access code reply message to be received from the access server using the non-voice network interface on a non-voice network.
- The access code may include a telephone number identifying a channel operably configured to cooperate with an IP network to cause a call involving the mobile telephone and the callee to be routed through the IP network.
- The network interface may include a mobile telephone network interface, and the codes for directing the processor circuit to initiate may include codes for directing the processor circuit to cause a call to be initiated using the mobile telephone network interface on a mobile telephone network.
- In accordance with another aspect, there is provided a system for initiating a call to a callee. The system includes: the mobile telephone; a routing controller; and an access server comprising a processor circuit and a computer readable medium in communication with the processor circuit. The computer readable medium is encoded with codes for directing the processor circuit to: receive from the mobile telephone the access code request message; communicate with the routing controller to obtain from the routing controller the access code wherein the access code identifies a channel and is useable by the mobile telephone to cause the routing controller to establish a call to the callee using the channel; and transmit the access code reply message to the mobile telephone.
- In accordance with another aspect, there is provided a computer readable medium encoded with codes for directing a processor circuit to: receive, from a user of a mobile telephone, a callee identifier associated with a callee; transmit an access code request message to an access server, the access code request message including the callee identifier; receive an access code reply message from the access server in response to the access code request message, the access code reply message including an access code different from the callee identifier and associated with the callee identifier; and initiate a call using the access code to identify the callee.
- In accordance with another aspect, there is provided a method for enabling a mobile telephone to initiate a call to a callee through a channel. The method involves: receiving from the mobile telephone an access code request message including a callee identifier associated with the callee; communicating with a routing controller to obtain from the routing controller an access code identifying the channel, the access code being different from the callee identifier and useable by the mobile telephone to initiate a call to the callee using the channel; and transmitting an access code reply message including the access code to the mobile telephone.
- Receiving may involve receiving the access code request message on a non-voice network.
- The method may further involve causing the routing controller to produce the access code.
- Producing may involve selecting the access code from a pool of access codes, where each access code in the pool of access codes identifies a respective telephone number.
- The method may further involve determining a local calling area associated with the mobile telephone.
- Determining may involve accessing a dialing profile associated with the caller, the dialing profile including a location field having contents identifying at least a default location of the caller.
- Determining may involve receiving an IP address of the mobile telephone in a wireless IP network.
- Determining may involve receiving an identifier of a wireless voice signal station in wireless communication with the mobile telephone.
- Determining may involve receiving a user-configured identifier of a location associated with the mobile telephone.
- Selecting may involve selecting an access code in the local calling area associated with the mobile telephone.
- Each access code in the pool of access codes may further identify a respective channel operably configured to cooperate with an IP network to cause a call involving the mobile telephone and the callee to be routed through the IP network.
- The method may further involve causing the routing controller to establish communication through the IP network in response to a call received on the channel.
- Producing may further involve storing a caller identifier associated with the mobile telephone in association with the access code.
- Causing the routing controller to establish communication may involve causing the routing controller to establish communication only if the caller identifier associated with the access code identifies the mobile telephone.
- Producing may further involve storing the callee identifier in association with the access code.
- Producing may further involve searching the pool of access codes for an access code associated with the callee identifier to identify the channel usable by the mobile telephone to initiate a call to the callee.
- Producing may further involve storing, in association with the access code, a timestamp for use in determining when the usability of the access code to initiate a call to the callee will expire.
- Causing the routing controller to establish communication may involve causing the routing controller to establish communication only if the usability of the access code to initiate a call to the callee has not expired.
- Transmitting may involve transmitting the access code reply message on a non-voice network.
- In accordance with another aspect, there is provided a system for enabling a mobile telephone to initiate a call to a callee through a channel. The system includes: provisions for receiving from the mobile telephone an access code request message including a callee identifier associated with the callee; provisions for communicating with the routing controller to obtain from the routing controller an access code identifying the channel, the access code being different from the callee identifier and useable by the mobile telephone to initiate a call to the callee using the channel; and provisions for transmitting an access code reply message including the access code to the mobile telephone.
- The provisions for receiving may include a non-voice network interface for receiving the access code request message on a non-voice network.
- The system may further include provisions for producing the access code.
- The provisions for producing may include a processor circuit operably configured to select the access code from a pool of access codes, where each access code in the pool of access codes identifies a respective telephone number.
- The processor circuit may be operably configured to determine a local calling area associated with the mobile telephone.
- The processor circuit may be operably configured to determine a local calling area associated with the mobile telephone using a dialing profile associated with the caller, the dialing profile including a location field having contents identifying at least a default location of the caller.
- The processor circuit may be operably configured to determine a local calling area associated with the mobile telephone using an IP address of the mobile telephone in a wireless IP network.
- The processor circuit may be operably configured to determine a local calling area associated with the mobile telephone using an identifier of a wireless voice signal station in wireless communication with the mobile telephone.
- The processor circuit may be operably configured to determine a local calling area associated with the mobile telephone using a user-configured identifier of a location associated with the mobile telephone.
- The processor circuit may be operably configured to select an access code in the local calling area associated with the mobile telephone.
- Each access code in the pool of access codes may further identify a respective channel operably configured to cooperate with an IP network to cause a call involving the mobile telephone and the callee to be routed through the IP network.
- The processor circuit may be operably configured to establish communication through the IP network in response to a call received on the channel.
- The processor circuit may be operably configured to store a caller identifier associated with the mobile telephone in association with the access code.
- The processor circuit may be operably configured to cause the routing controller to establish communication only if the caller identifier associated with the access code identifies the mobile telephone.
- The processor circuit may be operably configured to store the callee identifier in association with the access code.
- The processor circuit may be operably configured to search the pool of access codes for an access code associated with the callee identifier to identify the channel usable by the mobile telephone to initiate a call to the callee.
- The processor circuit may be operably configured to store, in association with the access code, a timestamp for use in determining when the usability of the access code to initiate a call to the callee will expire.
- The processor circuit may operably configured to establish communication only if the usability of the access code to initiate a call to the callee has not expired.
- The provisions for transmitting may include a non-voice network interface for transmitting the access code reply message on a non-voice network.
- In accordance with another aspect, there is provided a system for enabling a mobile telephone to initiate a call to a callee through a channel. The system includes a processor circuit, a network interface in communication with the processor circuit, and a computer readable medium in communication with the processor circuit and encoded with codes for directing the processor circuit to: receive from the mobile telephone an access code request message including a callee identifier associated with the callee; communicate with the routing controller to obtain from the routing controller an access code identifying the channel, the access code being different from the callee identifier and useable by the mobile telephone to initiate a call to the callee using the channel; and cause an access code reply message including the access code to be transmitted to the mobile telephone.
- The network interface may include a non-voice network interface, and the codes for directing the processor circuit to receive may include codes for directing the processor circuit to cause the access code request message to be received using the non-voice network interface on a non-voice network.
- The computer readable medium may be further encoded with codes for directing the processor circuit to cause the access code to be produced.
- The codes for directing the processor circuit to cause the access code to be produced may cause the access code to be selected from a pool of access codes, where each access code in the pool of access codes identifies a respective telephone number.
- The computer readable medium may be further encoded with codes for directing the processor circuit to cause to be determined a local calling area associated with the mobile telephone.
- The codes for directing the processor circuit to cause to be determined may cause a dialing profile associated with the caller to be accessed, the dialing profile including a location field having contents identifying at least a default location of the caller.
- The codes for directing the processor circuit to cause to be determined may cause to be received an IP address of the mobile telephone in a wireless IP network.
- The codes for directing the processor circuit to cause to be determined may cause to be received an identifier of a wireless voice signal station in wireless communication with the mobile telephone.
- The codes for directing the processor circuit to cause to be determined may cause to be received a user-configured identifier of a location associated with the mobile telephone.
- The codes for directing the processor circuit to cause the access code to be produced may further cause to be selected an access code in the local calling area associated with the mobile telephone.
- Each access code in the pool of access codes may further identify a respective channel operably configured to cooperate with an IP network to cause a call involving the mobile telephone and the callee to be routed through the IP network.
- The computer readable medium may be further encoded with codes for directing the processor circuit to cause communication through the IP network to be established in response to a call received on the channel.
- The codes for directing the processor circuit to cause the access code to be produced may cause a caller identifier associated with the mobile telephone to be stored in association with the access code.
- The codes for directing the processor circuit to cause communication to be established may cause communication to be established only if the caller identifier associated with the access code identifies the mobile telephone.
- The codes for directing the processor circuit to cause the access code to be produced may cause the callee identifier to be stored in association with the access code.
- The codes for directing the processor circuit to cause the access code to be produced may cause the pool of access codes to be searched for an access code associated with the callee identifier to identify the channel usable by the mobile telephone to initiate a call to the callee.
- The codes for directing the processor circuit to cause the access code to be produced may cause a timestamp for use in determining when the usability of the access code to initiate a call to the callee will expire, to be stored in association with the access code.
- The codes for directing the processor circuit to cause communication to be established may cause communication to be established only if the usability of the access code to initiate a call to the callee has not expired.
- The network interface may include a non-voice network interface, and the codes for directing the processor circuit to transmit include codes for directing the processor circuit to cause the access code reply message to be transmitted using the non-voice network interface on a non-voice network.
- In accordance with another aspect, there is provided a computer readable medium encoded with codes for directing a processor circuit to: receive from the mobile telephone an access code request message including a callee identifier associated with the callee; communicate with the routing controller to obtain from the routing controller an access code identifying the channel, the access code being different from the callee identifier and useable by the mobile telephone to initiate a call to the callee using the channel; and cause an access code reply message including the access code to be transmitted to the mobile telephone.
- Other aspects and features will become apparent to those ordinarily skilled in the art upon review of the following description of specific embodiments of the invention in conjunction with the accompanying figures.
- In drawings which illustrate embodiments,
-
FIG. 1 is a block diagram of a system for enabling a mobile telephone to initiate a call through a channel to a callee in accordance with a first embodiment in the invention; -
FIG. 2 is a block diagram of mobile telephone shown inFIG. 1 ; -
FIG. 3 is a flow chart of a process executed by the mobile telephone shown inFIG. 1 ; -
FIG. 4 is a schematic representation of an access code request message transmitted between the mobile telephone and an access server shown inFIG. 1 ; -
FIG. 5 is a schematic representation of an access code reply message transmitted between the mobile telephone and the access server shown inFIG. 1 ; -
FIG. 6 is a block diagram of the access server shown inFIG. 1 ; -
FIG. 7 is a flow chart of a process executed by the access server shown inFIG. 1 ; -
FIG. 8 is a block diagram of a routing controller shown inFIG. 1 ; -
FIG. 9 is a tabular representation of a dialing profile stored in a database accessible by the routing controller illustrated inFIG. 1 ; -
FIG. 10 is a tabular representation of an access code association table stored in memory accessible by the routing controller shown inFIG. 1 ; -
FIG. 11 is a schematic representation of a DID bank table record stored in a database shown inFIG. 1 ; -
FIG. 12 is a flow chart of a process executed by the routing controller illustrated inFIG. 1 ; -
FIG. 13 is a block diagram of a gateway shown inFIG. 1 ; -
FIG. 14 is a tabular representation of an SIP invite message transmitted between the gateway and a call controller illustrated inFIG. 1 ; -
FIG. 15 is a block diagram of the call controller illustrated inFIG. 1 ; -
FIG. 16 is a flow chart of a process executed by the call controller illustrated inFIG. 1 ; -
FIG. 17 is a tabular representation of an RC request message transmitted between the call controller and the routing controller illustrated inFIG. 1 ; -
FIGS. 18A-18C are a flow chart of a process executed by the routing controller illustrated inFIG. 1 ; and -
FIG. 19 is a tabular representation of a gateway node association table stored in the database illustrated inFIG. 1 . - Referring to
FIG. 1 , a system for enabling a mobile telephone to initiate a call to a callee is shown generally at 10. Thesystem 10 includes afirst node 11, asecond node 21, and amobile telephone 12. - The first and
second nodes first node 11 is located in a geographical area, such as Vancouver, British Columbia, Canada, for example, and thesecond node 21 is located in London, England, for example. Different nodes may be located in different geographical regions throughout the world to provide telephone/videophone service to subscribers in respective regions. These nodes may be in communication with each other by high speed/high data throughput links including optical fiber, satellite, and/or cable links illustrated generally at 17, forming a backbone to the system. These nodes may alternatively, or in addition, be in communication with each other through conventional internet services. - In the embodiment shown, the
first node 11 provides telephone/videophone service to western Canadian customers from Vancouver Island to Ontario. Another node (not shown) may be located in Eastern Canada to provide services to subscribers in that area, for example. - Other nodes of the type shown may also be employed within the geographical area serviced by a node to provide for call load sharing, for example, within a region of the geographical area serviced by the node. However, in general, all nodes may be similar and have the properties described in connection with the
first node 11. - In this embodiment, the
first node 11 includes a call controller (CC) 13, anaccess server 14, a routing controller (RC) 30, adatabase 23, avoicemail server 19, and amedia relay 28. Each of these may be implemented as separate modules on a common computer system or by separate computers, for example. Thevoicemail server 19 need not be included in the node and can be provided by a third party service provider. Although theaccess server 14 is illustrated as being part of thefirst node 11, access servers in alternative embodiments may be separate from the node and may be in communication with one or more nodes, for example. - The
mobile telephone 12 is configured to place calls over a mobile telephone network, illustrated generally at 15, in a manner well-known in the art. Furthermore, themobile telephone 12 and theaccess server 14 are configured to communicate with each other, preferably on a non-voice network illustrated generally at 16, such as a “WiFi” wireless IP network or a General Packet Radio Service (GPRS) network, for example. However, in alternative embodiments, themobile telephone 12 and theaccess server 14 may communicate with each other over other networks, such as a mobile telephone network using Short Message Service (SMS) messages, for example. - The
system 10 further includes agateway 18 in communication with at least one, and preferably a plurality of, channels, which are illustrated schematically at 20, 22, and 24, to which themobile telephone 12 may initiate a call over themobile telephone network 15. Thechannels channels mobile telephone 12, and thus these channels preferably depend on a geographical location of the mobile telephone. The expression “local calling area” herein refers generally to a set of telephone numbers, typically defined by a geographical region, to which telephone calls may be placed by callers within the local calling area at either no additional charge or at a lower additional charge than would be required for calls to numbers that are outside of the local calling area. However, it will be appreciated that in other embodiments, thegateway 18 may be in communication with any number of channels, which need not be PSTN telephone lines. Also, in the illustrated embodiment, thechannels mobile telephone 12. - In the illustrated embodiment, each of the
channels gateway 18. In the illustrated embodiment, the PSTN service provider has configured thechannels T1 multiplexer 25, which multiplexes thechannels more T1 lines 27 that are in communication with thegateway 18. Thegateway 18 is in communication with an IP network shown generally at 26. Thechannels gateway 18 in the illustrated embodiment) to cause a call involving themobile telephone 12 and the callee to be routed through the IP network in response to a call received at one of the channels. - Also, in the illustrated embodiment, the
access server 14 is in communication with therouting controller 30 of thefirst node 11, and therouting controller 30 is configurable to associate a callee identifier with one of thechannels channels PSTN telephone 32 that is in communication with theIP network 26 through agateway 34, or it may be a telephone number of aVoIP telephone 36 that is directly in communication with theIP network 26, for example.Other routing controllers 30 of other nodes, such as thesecond node 21, for example, may also associate callee identifiers with other channels that are in communication with other gateways (not shown). - Referring to
FIG. 2 , in this embodiment, the mobile telephone (12) includes a processor circuit shown generally at 50. Theprocessor circuit 50 includes amicroprocessor 52, aprogram memory 54, an input/output (I/O)port 56,parameter memory 58, andtemporary memory 60. Theprogram memory 54, I/O port 56,parameter memory 58, andtemporary memory 60 are all in communication with themicroprocessor 52. Theprocessor circuit 50 may alternatively include a plurality of processors, a plurality of program memories, a plurality of temporary memories, and/or a plurality of I/O ports, or these components may alternatively be combined into a single device. However, for simplicity, the components of theprocessor circuit 50 are illustrated as shown in the example ofFIG. 2 . - In the illustrated embodiment, the I/
O port 56 includes a dialinginput 62 for receiving a callee identifier from a key pad, for example, or from a voice recognition unit, or from pre-stored callee identifiers stored in theparameter memory 58, for example. For illustration purposes only, a myriad of possible dialing functions for providing a callee identifier are represented by the block entitled dialingfunction 64. A callee identifier may be a telephone number of a callee, for example. - The I/
O port 56 also includes ahandset interface 66 for receiving and producing signals to and from ahandset 68 that may be placed close to the user's ear and mouth, for producing and receiving audible signals for and from the user. It will be appreciated that alternatively, thehandset 68 may include a camera and video screen, for example, and that video or other types of signals may be transmitted additionally or alternatively to audible signals. - The I/
O port 56 also includes anon-voice network interface 70 for transmitting information to, and receiving information from, thenon-voice network 16 illustrated inFIG. 1 , for example, and preferably interfaces with a high-speed internet connection. - The I/
O port 56 in the illustrated embodiment further includes a mobiletelephone network interface 72 for transmitting signals to and receiving signals from a mobile telephone service provider over a network such as a Global System for Mobile communications (GSM) or a Code Division Multiple Access (CDMA) network, such as themobile telephone network 15 illustrated inFIG. 1 , for example. Again, for simplicity, a mobile telephone network interface is illustrated, although it will be appreciated that video signals or other signals may be handled similarly when the mobile telephone (12) is facilitating communication of one or more of these types of signals. It will also be appreciated that alternatively, thenon-voice network interface 70 and mobiletelephone network interface 72 need not be distinct, but may be a single interface for communication over a single network, for example, or may be configured to communicate over a plurality of different networks, for example. - In the illustrated embodiment, the
parameter memory 58 includes a username field 74 and a password field 76, although it will be appreciated that the username and password may not be necessary, or may be input by the user as required, for example. Theparameter memory 58 in the illustrated embodiment also includes acaller identifier field 78 for storing a caller identifier, which may be a telephone number associated with the mobile telephone (12) for identifying a “channel” such as a telephone line assigned to the mobile telephone that may be used to call back to the mobile telephone, for example. Generally, the contents of the username field 74, the password field 76, and thecaller identifier field 78 are set once when the user first subscribes to the system. - The usernames referred to herein, such as the username in the username field 74, preferably include a twelve digit number such as 2001 1050 8667, for example, wherein the left-most digit is a continent code (such as “2” to indicate North America, for example), followed by a three-digit country code (such as “001” to indicate Canada and the United States, for example), a four-digit dealer code (such as “1050”, for example), and a unique four-digit number code (such as “8667”, for example), as discussed more generally in PCT Publication No. 2008/052340. Therefore, a prefix of a username referred to herein preferably indicates a geographical region associated with the user, or with the access code, and more preferably indicates a node associated with the user or access code.
- The
program memory 54 stores blocks of codes for directing themicroprocessor 52 to carry out the functions of the mobile telephone (12), which are illustrated by example below. - Referring to
FIGS. 2 and 3 , a flow chart representing functions performed by blocks of code that direct themicroprocessor 52 to initiate a call with themobile telephone 12 to a callee is shown generally at 100. The blocks shown inFIG. 3 generally represent codes that may be stored in theprogram memory 54 for example, for directing themicroprocessor 52 to perform various functions relating to initiating a call with the mobile telephone (12) to a callee. The actual code to implement each block may be written in any suitable programming language, such as Java, C, and/or C++, for example. - The
process 100 begins at 102, in response to an interrupt produced at or for themicroprocessor 52 by the dialingfunction 64. Upon initiation of theprocess 100, block 104 directs themicroprocessor 52 to obtain a callee identifier from the dialingfunction 64 at the dialinginput 62 of the I/O port 56 in the illustrated embodiment. The callee identifier is associated with a desired callee, and may be a telephone number of the callee, for example. Themicroprocessor 52 thus receives, from a user of the mobile telephone (12), a callee identifier associated with a callee. -
Block 106 directs themicroprocessor 52 to transmit, using thenon-voice network interface 70 in the illustrated embodiment, an access code request message, the access code request message including the callee identifier obtained atblock 104, to the access server 14 (illustrated inFIG. 1 ). In general, preferably block 106 directs themicroprocessor 52 to cause an access code request message to be transmitted to theaccess server 14 over a non-voice network, such as an internet, using WiFi or GPRS technology for example. However, it will be appreciated thatblock 106 may direct themicroprocessor 52 to transmit an access code request message to theaccess server 14 using any suitable technique, which may alternatively include a voice network, for example. - Referring to
FIG. 4 , an exemplary access code request message is shown generally at 110. The accesscode request message 110 includes ausername field 112, a password field 114, acallee identifier field 116, and acaller identifier field 118. In the illustrated embodiment, values for the username, password, and caller identifier fields 112, 114, and 118 are retrieved from the username, password, and caller identifier fields 74, 76, and 78 respectively in theparameter memory 58 of the processor circuit 50 (illustrated inFIG. 2 ), and a value for thecallee identifier field 116 is obtained from the dialingfunction 64 inblock 104, and may be stored in the temporary memory (60), for example. It will be appreciated that theusername field 112, password field 114, andcaller identifier field 118 are not essential, although these fields are preferable in order to identify the user of the mobile telephone for billing purposes, for example. - Referring to
FIGS. 1 and 4 , it will be appreciated that in order to minimize charges from the mobile telephone service provider of themobile telephone 12, thechannels mobile telephone 12. Therefore, the exemplary accesscode request message 110 further includes alocation identifier field 119. The location identifier stored in thelocation identifier field 119 preferably identifies a location of themobile telephone 12 for use in determining a local calling area associated with themobile telephone 12. - For example, the location identifier in the
location identifier field 119 may include an IP address of themobile telephone 12 in a wireless IP network, such as thenon-voice network 16 to which thenon-voice network interface 70 shown inFIG. 2 is connected, because this IP address may be an indicator of a geographical location of themobile telephone 12. The location identifier may also or alternatively include an identifier of a wireless voice signal station in wireless communication with the mobile telephone. In the illustrated embodiment, the wireless voice signal station is part of themobile telephone network 15 that is in communication with themobile telephone 12 through the mobiletelephone network interface 72 illustrated inFIG. 2 . In still other embodiments, the location identifier may include a user-configured identifier of a geographical location or local calling area where themobile telephone 12 is or may be situated. The location identifier may thus be pre-determined and stored in theparameter memory 58 shown inFIG. 2 or may be acquired from non-voice network or wireless voice signal station or from user input, for example. Therefore, in summary, the location identifier in thelocation identifier field 119 may include one or more of an IP address of themobile telephone 12 in a wireless IP network, an identifier of a wireless voice signal station in wireless communication with the mobile telephone, and a user-configured identifier. - As described below, the location identifier in the
location identifier field 119 may be used to determine a local calling area associated with themobile telephone 12, within which local calling area channels (illustrated as 20, 22, and 24 inFIG. 1 ) are available to themobile telephone 12 for the lowest cost to the user. However, it will be appreciated that the location identifier may only approximately identify a local calling area, and may not necessarily identify the lowest cost channel (illustrated as 20, 22, and 24 inFIG. 1 ) for themobile telephone 12. It will also be appreciated that in other embodiments, thelocation identifier field 119 may be omitted. - Referring back to
FIG. 3 , theprocess 100 continues atblock 130, which directs the microprocessor (52) to receive an access code reply message from the access server (14) in response to the access code request message that was transmitted atblock 106. - Referring to
FIG. 5 , an exemplary access code reply message is shown generally at 140. The accesscode reply message 140 includes anaccess code field 142 and atimeout field 144. In the illustrated embodiment, theaccess code field 142 stores an access code which is a telephone number associated with a telephone line associated with one of thechannels FIG. 1 . It will be appreciated that the access code is different from the callee identifier in thecallee identifier field 116 shown inFIG. 4 , in that the access code identifies a channel, other than that provided by the callee identifier provided by the dialingfunction 64 inFIG. 2 , that the mobile telephone (12) can use to initiate a call to the callee. It will be appreciated that use of the access code facilitates avoidance of long distance or roaming charges that a mobile telephone service provider would charge for a call placed directly using the callee identifier using conventional calling processes, for example. - Still referring to
FIG. 5 , thetimeout field 144 in the illustrated embodiment stores a value that indicates a period of time, for example a number of minutes, during which the access code in theaccess code field 142 is associated with the callee identifier in thecallee identifier field 116 of the exemplary accesscode request message 110 illustrated inFIG. 4 , such that the access code is only temporarily associated with the callee identifier. In one embodiment, the value stored in thetimeout field 144 indicates 10 minutes, for example. It will be appreciated that in other embodiments, thetimeout field 144 may not be necessary, but preferably it is included. - In the illustrated embodiment, the program codes in
block 130 direct themicroprocessor 52 to receive the access code reply message over a non-voice network, such as a WiFi or GPRS network (illustrated at 16 inFIG. 1 ) via thenon-voice network interface 70 shown inFIG. 2 . However, it will be appreciated that the access code reply message may be received on any suitable network, even a voice network, for example. - Referring back to
FIGS. 2 and 3 , block 149 directs themicroprocessor 52 to initiate a call with the mobile telephone (12) on the mobile telephone network 15 (illustrated inFIG. 1 ) using the access code received in theaccess code field 142 of the access code reply message 140 (shown inFIG. 5 ) to identify the callee. In the illustrated embodiment, the codes inblock 149 direct themicroprocessor 52 to initiate a call to the channel (20, 22, or 24) identified by the access code, using the mobiletelephone network interface 72 of the I/O port 56 of the mobile telephone (12), to engage the mobile telephone network (15). - Referring to
FIG. 1 , in the embodiment shown, the access code in the access code field (142) is a telephone number identifying achannel gateway 18 to theIP network 26. Through thegateway 18, thechannel IP network 26 to cause a call from themobile telephone 12 to the callee to be routed through the IP network. Routing the call through the IP network may involve engaging therouting controller 30 to route the call on theIP network 26 to the callee, as described below. However, it will be appreciated that in other embodiments, the access code need not be a telephone number, but may be any code identifying a channel through which themobile telephone 12 can initiate a call. Alternatively, if the mobile telephone is capable of voice over IP communications, the access code may be used to identify an IP address in the IP network to which the call is routed. In this embodiment, the IP address may act as the access code. Theprocess 100 shown inFIG. 3 is then ended. - Referring to
FIG. 6 , the access server (14) includes a processor circuit shown generally at 150. Theprocessor circuit 150 includes amicroprocessor 152,program memory 154, an I/O port 156,parameter memory 158, andtemporary memory 160. Theprogram memory 154, I/O port 156,parameter memory 158, andtemporary memory 160 are all in communication with themicroprocessor 152. Theprocessor circuit 150 may alternatively include a plurality of microprocessors or I/O ports, for example, and the components of the illustratedprocessor circuit 150 may also alternatively be combined into a single device. - The
program memory 154 stores blocks of codes for directing themicroprocessor 152 to carry out the functions of theaccess server 14. The I/O port 156 includes anon-voice network interface 162 for communicating with thenon-voice network 16 illustrated inFIG. 1 . The I/O port 156 also includes arouting controller interface 164 for interfacing with therouting controller 30 illustrated inFIG. 1 . - Referring to
FIGS. 6 and 7 , a flow chart of blocks of code for directing themicroprocessor 152 of the access server (14) to provide an access code to the mobile telephone (12) is shown generally at 190. Theblocks 190 inFIG. 7 generally represent codes that may be stored in theprogram memory 154 for directing themicroprocessor 152 to perform various functions to provide the access to the mobile telephone (12) to enable the mobile telephone to place a call through a channel (20, 22, or 24). - The
process 190 begins at 192, in response to an interrupt created by or for themicroprocessor 152 when it receives an access code request message 110 (as illustrated inFIG. 4 ) from the mobile telephone (12). In the illustrated embodiment, the access code request message (110) is received via thenon-voice network interface 162 through a non-voice network (16) such as a WiFi or GPRS network, for example. However, it will be appreciated that other embodiments may use different techniques for receiving the access code request message (110) from the mobile telephone (12). - The
process 190 continues atblock 196, which directs themicroprocessor 152 to communicate with therouting controller 30 to obtain from the routing controller an access code identifying a channel (illustrated as 20, 22, or 24 inFIG. 1 ) in communication with the gateway (18), wherein the access code is different from the callee identifier in the callee identifier field 116 (shown inFIG. 4 ) and is usable by the mobile telephone (12) to initiate a call to the callee using the channel, as further described below. Therefore, block 196 preferably causes an access code to be produced by retransmitting the accesscode request message 110 illustrated inFIG. 4 that was received at 192 from the mobile telephone (12), to therouting controller 30 through therouting controller interface 164 of the I/O port 156. - The
process 190 continues atblock 198, which directs themicroprocessor 152 to transmit an access code reply message (140), including the access code obtained byblock 196, to the mobile telephone (12). An exemplary access code reply message is shown inFIG. 5 . In the illustrated embodiment, an access code reply message (140) is produced by therouting controller 30 in a manner described below in response to the access code request message (110) that was transmitted to the routing controller atblock 196, and the access code reply message (140) is received from the routing controller through therouting controller interface 164 of the I/O port 156.Block 198 then causes the access code reply message that was received from the routing controller to be retransmitted to the mobile telephone (12). In the illustrated embodiment, the codes inblock 198 direct themicroprocessor 152 to transmit the access code reply message (140) using thenon-voice network interface 162 to thenon-voice network 16, which may be a WiFi or GPRS network, for example. However, it will be appreciated that other embodiments may employ other types of networks for communicating the access code reply message (140) to the mobile telephone (12). Theprocess 190 is then ended. - In summary, referring to
FIG. 1 , theaccess server 14 generally acts as an interface to therouting controller 30 for relaying access code request messages and access code reply messages between themobile telephone 12 and the routing controller. Therefore, it will be appreciated that in alternative embodiments, theaccess server 14 and therouting controller 30 need not be separate, but may, for example, be combined in a single component. - Referring to
FIG. 1 , generally, therouting controller 30 executes a process to facilitate communication between callers and callees. The function of a routing controller generally in a VoIP system is described in PCT Publication No. WO 2008/052340. - Referring to
FIG. 8 , the routing controller (30) includes a processor circuit shown generally at 230. Theprocessor circuit 230 includes a microprocessor (or more generally a processor) 232,program memory 234, an I/O port 236,table memory 238,temporary memory 240, and aclock 244. Theprogram memory 234, I/O port 236,table memory 238,temporary memory 240, andclock 244 are all in communication with theprocessor 232. Theprocessor circuit 230 may include a plurality of microprocessors, for example, and the aforementioned components of theprocessor circuit 230 may be combined, for example. Theprogram memory 234 includes blocks of code for directing theprocessor 232 to carry out the functions of the routing controller (30), and the I/O port 236 includes anaccess server interface 242 for communicating with theaccess server 14. - In the illustrated embodiment as described above, the access server (14) transmits (at
block 196 illustrated inFIG. 7 ) an access code request message (110) to the routing controller (30) in order to obtain from the routing controller (30) an access code. When an access code request message (110) is received at theaccess server interface 242, theprocessor 232 preferably stores certain values from the access code request message in stores in thetemporary memory 240 for ease of retrieval. In particular, thetemporary memory 240 includes acallee identifier store 246 for storing the callee identifier from thecallee identifier field 116 in the accesscode request message 110 illustrated inFIG. 4 , acaller identifier store 248 for storing the caller identifier that was stored in thecaller identifier field 118 of the accesscode request message 110 illustrated inFIG. 4 , acaller username store 249 for storing the caller username that was stored in thecaller username field 112 of the accesscode request message 110 illustrated inFIG. 4 , and anaccess code store 250 for storing an access code that is selected when the routing controller (30) receives an access code request message (110). Thetemporary memory 240 also includes a local callingarea identifier store 245 for storing an identifier of a local calling area associated with the mobile telephone (12). Theclock 244 generally maintains and stores a representation of a current date and time. - The I/O port 236 further includes a
database request port 256 through which a request to the database (23 inFIG. 1 ) can be made, and also includes adatabase response port 258 for receiving a reply from the database (23). The I/O port 236 further includes a routing controller (RC)request message input 260 for receiving an RC request message (illustrated inFIG. 17 ) from the call controller (13 inFIG. 1 ) and includes arouting message output 262 for sending a routing message back to thecall controller 13. The I/O port 236 thus acts to receive a caller identifier and a callee identifier contained in an RC request message from the call controller, the RC request message being received in response to initiation of a call by a subscriber of the system, as described below. - The
program memory 234 includes blocks of codes for directing theprocessor 232 to carry out various functions of the routing controller (30). One of these blocks includes an RCrequest message handler 380 which directs the routing controller (30) to produce a routing message in response to a received RC request message, an example of which is illustrated inFIG. 17 . The RC request message handler process is shown in greater detail at 380 inFIGS. 18A through 18C . Another of these blocks in theprogram memory 234 includes an access code generator, which is described at 270 inFIG. 12 , and which directs the routing controller (30) to produce an access code as directed by the program codes inblock 196 shown inFIG. 7 . Yet another of these blocks in theprogram memory 234 includes a local calling area identifier generator, which directs the routing controller (30) to produce a local calling area identifier using the location identifier from thelocation identifier field 119 of the accesscode request message 110 illustrated inFIG. 4 . - Referring to
FIG. 1 , it will be appreciated that preferably, a call made by themobile telephone 12 using the access code obtained from theaccess server 14 will be a local call for themobile telephone 12, based on a geographical location of the mobile telephone. Therefore, blocks in theprogram memory 234 include a local calling area identifier generator, which directs therouting controller 30 to produce a local calling area identifier. - For example, the local calling area identifier generator may direct the
microprocessor 152 to access a dialing profile associated with the caller. The dialing profile may be identified using the username in theusername field 112 in the accesscode request message 110 illustrated inFIG. 4 , and to store in the local calling area identifier field 245 a default location of the caller retrieved from the dialing profile associated with the caller. - Referring to
FIG. 9 , an exemplary dialing profile is illustrated generally at 200 and includes a username field 202, a domain field 204, and calling attributes comprising a national dialing digits (NDD)field 206, an international dialing digits (IDD) field 208, acountry code field 210, a local area codes field 212, a caller minimum local number length field 214, a caller maximum local number length field 216, areseller field 218, a maximum number ofconcurrent calls field 220, a current number ofconcurrent calls field 222, and a default local callingarea identifier field 224. Therefore, in some embodiments, the local calling area identifier generator directs themicroprocessor 152 to determine a local calling area associated with the mobile telephone (12) by retrieving the default local calling area identifier from the default local callingarea identifier field 224 of thedialing profile 200. - Effectively, the dialing
profile 200 is a record identifying calling attributes of the caller identified by the username in the username field 202. More generally, dialingprofiles 200 represent calling attributes of respective users, and are discussed in more detail in PCT publication No. WO 2008/052340. As described in PCT publication No. WO 2008/052340, a dialing profile of the type shown inFIG. 9 , and also other records such as direct-in-dial (DID) records, call blocking records, call forwarding records, and voicemail records, may be created whenever a user registers with the system or agrees to become a subscriber to the system. - Alternatively, the local calling area identifier generator may generate a local calling area identifier to be stored in the local calling
area identifier store 245 using the location identifier from thelocation identifier field 119 of the accesscode request message 110 illustrated inFIG. 4 . As described above, the location identifier field (119) may store one or more of an IP address of the mobile telephone (12) in a wireless IP network, an identifier of a wireless voice signal station in wireless communication with the mobile telephone, and a user-configured identifier. One or more of these values may be used to identify a local calling area that is or is likely to be associated with the mobile telephone (12) in order to generate a local calling area identifier to be stored in the local callingarea identifier store 245. - For example, it has been found that services available from web sites such as http://www.ip2location.com/ and http://www.serviceobjects.com/products/dots_ipgeo.asp, for example, can produce a name of a location, and also latitude and longitude values, associated with an IP address. Using this information derived from an IP address, or other information from the location identifier field (119), a local calling area may be identified by hierarchical jurisdictional designations (such as country, province, and city in Canada or country, state, and city in the United States) and encoded as codes identifying the local calling area. These codes may then be stored in the local calling
area identifier store 245. - In the illustrated embodiment, the table memory 238 (shown in
FIG. 8 ) includes an access code association table 170, an example of which is illustrated inFIG. 10 , for associating access codes with callee identifiers, caller identifiers, caller usernames, timeouts, and timestamps. Although the routing controller (30) is illustrated in this embodiment as a separate component from the access server (14), it will be appreciated that in other embodiments, the routing controller (30) may be part of or integrated with the access server (14), and in these other embodiments, the access code association table 170 may be part of or integrated with the access server. - Referring to
FIGS. 1 and 10 , the access code association table 170 generally includes a plurality of records, each having anaccess code field 173 storing an access code. The access codes in the access code association table 170 may thus form a pool of access codes, where each access code may identify a respective telephone number. In the illustrated embodiment, the access codes in theaccess code fields 173 of records of the access code association table 170 identify respective channels (illustrated by example only as 20, 22, and 24) that are operably configured to cooperate with theIP network 26 via thegateway 18 to cause a call involving themobile telephone 12 to be routed through the IP network. - Referring to
FIG. 10 , the exemplary access code association table 170 includesrecords calling area identifier 171, anaccess code 173, achannel identifier 175, acallee identifier 177, acaller identifier 179, acaller username 183, atimeout 181, and atimestamp 182. Generally, a record in the access code association table 170 will be created for each access code that identifies a channel (such as thechannels FIG. 1 ) that is configured or configurable to establish communication through a gateway (such as thegateway 18 illustrated inFIG. 1 ) to an IP network (26 inFIG. 1 ) in response to a call received at the channel. When a record is created in respect of a channel, the local callingarea identifier field 171 is preferably initialized with an identifier of a local calling area associated with the channel, theaccess code field 173 is preferably initialized with an access code associated with the channel, and thechannel identifier field 175 is preferably initialized with an identifier of the channel. The remaining fields (for storing acallee identifier 177, acaller identifier 179, acaller username 183, atimeout 181, and a timestamp 182) are preferably initialized with default “null” values when a record is created. The fields for storing a localcalling area identifier 171, anaccess code 173, achannel identifier 175 preferably remain generally constant during ordinary operation of the access code association table 170, although the values stored in the fields for storing acallee identifier 177, acaller identifier 179, acaller username 183, atimeout 181, and atimestamp 182 may vary as described below. It will be appreciated that in some embodiments, one or more of the fields for storing a localcalling area identifier 171, achannel identifier 175, acaller identifier 179, acaller username 183, atimeout 181, and atimestamp 182 may not be required and be omitted. - As noted above, the local calling
area identifier field 171 is preferably initialized with an identifier of a local calling area associated with the channel. The local callingarea identifier field 171 preferably stores codes that are encoded in the same manner as the codes in the local callingarea identifier store 245, as described above, so that an access code in the local calling area identified by the codes in the local callingarea identifier store 245 may be identified by searching the access code association table 170 for an access code associated with a local calling area identifier in the associated local callingarea identifier field 171 that matches the local calling area identifier in the local callingarea identifier store 245. It has been found that information available from web sites such as http://en.wikipedia.org/wiki/List_of_NANP_area_codes, and services available from web sites such as http://www.serviceobjects.com/demos/PhoneExchangeDemo.asp, for example, may be used to determine a local calling area identifier associated with a given access code where, for example, the access code is a PSTN telephone number. - In the exemplary access code association table 170, the access codes in the
access code fields 173 are telephone numbers for PSTN lines, three of which are in the 604 area code in Vancouver, British Columbia, Canada, and two of which are in the 416 area code in Toronto, Ontario, Canada. It will be appreciated that the access code association table 170 is an example only, and other access code association tables may include any number of access codes, which need not be PSTN telephone numbers, and which need not be limited to particular geographical areas. - In the exemplary access code association table 170, the
access code field 173 in the record 174 stores an access code 1-604-345-2323, which may be a local telephone number for Vancouver, British Columbia, Canada, and thecallee identifier field 177 of the record 174 stores a callee identifier 1-403-789-1234, which may be a telephone number for a callee in Calgary, Alberta, Canada for example, thereby associating the callee identifier 1-403-789-1234 with the access code 1-604-345-2323. Furthermore, thecaller identifier field 179 of the record 174 stores a caller identifier 1-416-444-1441 and thecaller username field 183 stores acaller username 2001 1050 8667, thereby associating the caller identifier 1-416-444-1441 andcaller username 2001 1050 8667 with the aforementioned access code and callee identifier. The caller identifier 1-416-444-1441 may be associated with a mobile telephone normally geographically located in Toronto, Ontario, Canada, but which may be in Vancouver and is therefore using a Vancouver-based access code to place a call to a Calgary-based number, for example. In theexample record 174, thetimestamp field 182 indicates that the callee identifier 1-403-789-1234, the caller identifier 1-416-444-1441, and thecaller username 2001 1050 8667 were associated with the access code 1-604-345-2323 on Jun. 15, 2008 at 10:31 am, and thetimeout field 181 indicates that this association is to expire 10 minutes after the time indicated in the timestamp field. - Likewise, the
exemplary record 178 indicates that the callee identifier 1-604-321-1234, the caller identifier 1-416-444-1234, and thecaller username 2001 1050 4141 were associated with the access code 1-416-234-4646 on Jun. 15, 2008 at 2:21 pm, and thetimeout field 181 of therecord 178 indicates that this association is to expire within 10 minutes of the time in thetimestamp field 182. - It will also be appreciated that the access code association table 170 may, in other embodiments, be substituted with other data structures or storage media. For example, in alternative embodiments, as described below, a DID record of the type shown at 370 in
FIG. 11 may associate an access code with a callee identifier and with other information such as a caller identifier, a timeout value, and a timestamp value, additionally or alternatively to the access code association table 170. - As described in PCT Publication No. 2008/052340, a DID bank table record may be created and stored in a DID bank table in the database (23 in
FIG. 1 ) when a user registers with the system, to associate the username of the user and a host name of the node with which the user is associated, with a number on the PSTN network formatted in compliance with the E.164 standard set by the International Telecommunication Union (ITU). However, as explained below, DID records may, in some embodiments, also associate usernames and host names with respective access codes, and may also associate access codes with respective callee identifiers and with other information such as caller identifiers, timeout values, and timestamp values. - Referring to
FIG. 11 , an exemplary DID bank table record is shown generally at 370, and includes ausername field 371, auser domain field 372, and a DIDfield 373. Theusername field 371 may store a username of a user of the system, in which case theuser domain field 372 stores a host name of the node with which the user is associated, and the DIDfield 373 stores an E.164 number on the PSTN network associated with the user. Exemplary host names stored in theuser domain field 372 include sp.yvr.digifonica.com for Vancouver, British Columbia, Canada and sp.lhr.digifonica.com for London England, for example, as described in PCT Publication No. 2008/052340. If the user has multiple telephone numbers, then multiple records of the type shown at 370 would be included in the DID bank table, each having the same username and user domain, but different DIDfield 373 contents reflecting the different telephone numbers associated with that user. - However, DID
fields 373 of DID bank table records 370 may also store access codes, in which case theusername field 371 may store a username associated with the access code. In these DID bank table records 370, theuser domain field 372 stores a host name of the node with which the access code is associated. Therefore, DID bank table records 370 may, in some embodiments, associate usernames and host names with respective access codes. - The exemplary DID
bank table record 370 further includes acallee identifier field 374, acaller identifier field 375, atimeout field 376, atimestamp field 377, a local callingarea identifier field 378, achannel identifier field 379, and acaller username field 381, which may be used in an analogous manner to thecallee identifier field 177, thecaller identifier field 179, thetimeout field 181, thetimestamp field 182, the local callingarea identifier field 171, thechannel identifier field 175, and thecaller username field 183 respectively of the access code association table 170 illustrated inFIG. 10 . The DID bank table records 370 may thus associate access codes with respective local calling area identifiers, callee identifiers, caller identifiers, caller usernames, timeouts, and timestamps, although thecaller identifier field 375,timeout field 376,timestamp field 377, local callingarea identifier field 378,channel identifier field 379, andcaller username field 381 may not be necessary, and one or more of these fields may be omitted in some embodiments. - Furthermore, it will be appreciated that the
callee identifier field 374,caller identifier field 375,timeout field 376, andtimestamp field 377 of the DIDbank table record 370 may be omitted for DID table records that are not in respect of access codes, but rather are in respect of telephone numbers of users of the system, for example, as described in PCT Publication No. 2008/052340. Thecallee identifier field 374,caller identifier field 375,timeout field 376, andtimestamp field 377 of the DIDbank table record 370 may also be omitted in embodiments where the access code association table 170 includes records with these types of fields. - For simplicity, the following description is directed to embodiments wherein an access code association table 170 associates access codes with respective callee identifiers, caller identifiers, timeout values, and timestamp values. However, it will be appreciated that the processes described herein for records in the access code association table 170 may additionally or alternatively be applied to DID
bank table records 370 in an analogous manner. - Referring back to
FIGS. 1, 4, and 8 in the illustrated embodiment as described above, theaccess server 14 transmits (atblock 196 illustrated inFIG. 7 ) an accesscode request message 110 to therouting controller 30 in order to obtain from therouting controller 30 an access code. When an accesscode request message 110 is received at theaccess server interface 242, theprocessor 232 preferably authenticates the user by making various enquiries of databases to which it has access, to determine whether or not the password in the password field 114 of the accesscode request message 110 matches a password stored in the database in association with the username in theusername field 112. Various functions may be used to pass encryption keys or hash codes back and forth to ensure that the transmittal of passwords is secure. If the user is successfully authenticated, theprocessor 232 then preferably produces an access code. - Referring to
FIGS. 8 and 12 , a process for producing an access code is shown generally at 270. Essentially theprocess 270 determines whether the access code in a given record (referred to below as the “currently addressed record”) in the access code association table shown at 170 inFIG. 10 is within the local calling area identified by the local callingarea identifier store 245, and whether the access code is currently available for association with a callee identifier. In order to produce an access code in response to receiving an access code request message (110) from the access server (14), theprocessor 232 of the routing controller (30) preferably searches the pool of access codes in the access code association table (170) to identify an access code identifying a channel usable by the mobile telephone (12) to initiate a call to the callee, using theprocess 270 until an available access code in the local calling area identified by the local callingarea identifier store 245 is identified. The access code generator thus preferably selects an access code from the pool of access codes in the access code association table (170), and preferably selects an access code in a local calling area associated with the mobile telephone (12). - Starting with the first record in the access code association table, the
process 270 begins atblock 272, which directs theprocessor 232 of the routing controller (30) to determine whether the access code in the currently addressed record of the access code association table 170 is associated with the same local calling area as the mobile telephone (12) as identified by the contents of the local callingarea identifier store 245. If atblock 272 the access code of the currently addressed record is not associated with the same local calling area as the mobile telephone (12), theprocess 270 ends, the next record in the access code association table 170 is addressed, and the process is repeated for the next record in the access code association table. - However, if at
block 272 the access code of the currently addressed record is associated with the same local calling area as the mobile telephone (12), or if the access code request message 110 (illustrated inFIG. 4 ) did not include a local calling area identifier, then theprocess 270 continues atblock 274, which directs theprocessor 232 to determine whether the access code of the currently addressed record is associated with a callee identifier. To do this, theprocessor 232 determines whether the callee identifier field (177) of the currently addressed record stores a “null” value that was assigned to it on initialization, or whether the callee identifier field instead stores a callee identifier. In other words the processor checks to see whether the currently addressed record has already been in use. - If at
block 274 the callee identifier field (177) of the currently addressed record in the access code association table (170) does store a callee identifier and not the “null” value that was assigned to the callee identifier field on initialization (for example,records FIG. 10 ), then the access code of that record is associated with a callee identifier, and theprocess 270 continues atblock 278, which directs theprocessor 232 to determine whether the association of the callee identifier with the access code has expired. In the illustrated embodiment, the codes atblock 278 direct theprocessor 232 to determine whether the sum of the contents of the timestamp field (182) and of the timeout field (181) in the currently addressed record of the access code association table 170 (shown inFIG. 10 ) is less than the current time represented by theclock 244. If atblock 278 the sum of the timeout and timestamp fields in the currently addressed record of the access code association table 170 is less than the time represented by theclock 244, then the association of the callee identifier with the access code is not expired and theprocess 270 ends, the next record in the access code association table (170) is addressed, and theprocess 270 is repeated for the next record in the access code association table. - However, if at
block 278 the sum of the contents of the timeout and timestamp fields (181 and 182) in the currently addressed record of the access code association table (170) is not less than the time represented by theclock 244, then the association of the callee identifier with the access code has expired, and theprocess 270 continues atblock 276 which directs theprocessor 232 to store the contents of theaccess code field 173 of the currently addressed record in theaccess code store 250 of thetemporary memory 240 of therouting controller 30. - Referring to
FIGS. 8, 10, and 12 , if atblock 274 the callee identifier field in the currently addressed record does not store a callee identifier but stores instead the “null” value that was assigned to the callee identifier field on initialization (for example,records process 270 continues atblock 276, which directs theprocessor 232 to store the access code from theaccess code field 173 of the currently addressed record, in theaccess code store 250 in thetemporary memory 240. - After the selected access code is stored in the
access code store 250 atblock 276, theprocess 270 continues atblock 280, which directs theprocessor 232 to store the callee identifier from thecallee identifier store 246 in thecallee identifier field 177 of the currently addressed record, thereby creating an association of the callee identifier with the selected access code. - The
process 270 then continues atblock 282, which directs theprocessor 232 to store the caller identifier from the caller identifier store 248 (which identifies themobile telephone 12 shown inFIG. 1 ) in thecaller identifier field 179 of the currently addressed record of the access code association table 170, thereby also storing the caller identifier in association with the selected access code. - The
process 270 then continues at block 283, which directs theprocessor 232 to store the caller username from thecaller username store 249 in thecaller username field 183 of the currently addressed record of the access code association table 170, thereby also storing the caller username in association with the selected access code. - The
process 270 then continues atblock 284, which directs theprocessor 232 to store timeout and timestamp values in the timeout andtimestamp fields timeout field 181 of the currently addressed record. Also, the current time indicated by theclock 244 is preferably stored in thetimestamp field 182 of the currently addressed record. - In alternative embodiments, the access code association table (170) might not include fields for a caller identifier, caller username, a timeout, or a timestamp. In these embodiments, one or more of
blocks caller identifier store 248 and thecaller username store 249 may be omitted. - In summary, the access code generator in the illustrated embodiment responds to receiving an access
code request message 110 illustrated inFIG. 4 from the access server (14) by first authenticating the user, and then by searching through a pool of access codes, using theprocess 270 shown inFIG. 12 , to identify an access code that is associated with the local calling area identified by the local calling area identifier store (245) and that is not previously and validly associated with another callee identifier. It will be appreciated that in alternative embodiments, different data structures and algorithms may be preferable for identifying an access code that meets the aforementioned criteria. For example, in accordance with conventional database design that is well-known in the art, the records illustrated in the access code association table 170 illustrated inFIG. 10 may alternatively be organized in a binary tree according to the value in the local callingarea identifier field 171, or in separate tables for respective local calling area identifiers, for example, in order to enable a more efficient search of the access code association table for an access code that satisfies the aforementioned criteria. Therefore, the access code association table (170) and theprocess 270 illustrated inFIG. 12 are examples only, and one of ordinary skill in the art will readily appreciate numerous alternative data structures and algorithms. - Referring to
FIG. 13 , in this embodiment, the gateway (18) includes a processor circuit shown generally at 300, which includes amicroprocessor 302. Theprocessor circuit 300 also includes aprogram memory 304, amemory 305, and an I/O port 306, all of which are in communication with themicroprocessor 302. Theprocessor circuit 300 may include multiple processors etc., and the aforementioned components of theprocessor circuit 300 may alternatively be combined. - The I/
O port 306 includes achannel interface 308, which, in the illustrated embodiment, is in communication with thechannels FIG. 1 . Where, as in the illustrated embodiment, thechannels PSTN network 29, thechannel interface 308 may, for example, be a T1 port for communication with one or more T1 lines (illustrated at 27 inFIG. 1 ) of a PSTN service provider, in a manner well-known in the art. The I/O port in the illustrated embodiment also includes aninternet interface 309 for interfacing with the Internet Protocol (IP)network 26 illustrated inFIG. 1 . Theprogram memory 304 stores blocks of codes for directing themicroprocessor 302 to carry out the functions of the gateway (18). It has been found that the AS5350 Universal Gateway available from Cisco Systems, Inc. of San Jose, Calif. may, for example, be suitable as the gateway (18). - Referring back to
FIG. 1 , and also still toFIG. 13 , when a call is received on one of thechannels microprocessor 302 causes the I/O port 306 to use theinternet interface 309 to send a Session Initiation Protocol (SIP) Invite message to a pre-determined node with which thegateway 18 is associated, which in the illustrated embodiment is thefirst node 11. Generally, thegateway 18 will be associated with a node that is geographically closest to the gateway, in order to minimize transmission times over theIP network 26. In response to the SIP Invite message, thecall controller 13 sends an RC request message to therouting controller 30 which makes various enquiries of thedatabase 23 to produce a routing message that is sent back to thecall controller 13. Thecall controller 13 then communicates with themedia relay 28 to cause a communications link including an audio path (and a videopath if a videophone call) to be established through the media relay to the same node, a different node, or to a communications supplier gateway as shown generally at 34 to carry audio, and where applicable, video traffic to the call recipient or callee. - Referring to
FIG. 14 , an exemplary SIP Invite message is shown generally at 310 and includes acaller identifier field 312, acallee identifier field 314, a digestparameter field 315, acall identifier field 316, anIP address field 317, and a gatewayUDP port field 318. Examples of values for the fields in theSIP Invite message 310 are shown for illustration purposes only inFIG. 14 . The caller identifier in thecaller identifier field 312 is preferably in the form of the telephone number of the caller followed by the “@” symbol, which in turn is followed by the IP address of the gateway (18) in the IP network (26). The caller identifier may be determined by retrieving calling line identification (CLID) information from the signal provided by the PSTN network (29) to the gateway (18) for example. Where the caller identification information is not available to the gateway (18), the caller identifier in thecaller identifier field 312 preferably includes a pre-assigned number (such as 11111, for example) indicating that the caller identification information was not available, followed by the “@” symbol and then by the IP address of the gateway (18). - The callee identifier in the
callee identifier field 314 is the access code identifying the channel (20, 22, or 24 in the example ofFIG. 1 ) on which the call was placed, and which was received from the access server (14). In the illustrated example, the access code is the PSTN telephone number 1-604-345-1212 corresponding to thechannel 20 illustrated inFIG. 1 , and to the access code stored in theaccess code field 173 of therecord 172 in the exemplary access code association table 170 illustrated inFIG. 10 . - The digest parameter in the digest
parameter field 315 is generated by the gateway (18) and may uniquely identify the SIP session that is initiated with theSIP Invite message 310. - The call identifier in the
call identifier field 316 is, in the illustrated embodiment, a four-digit hexadecimal number generated by the gateway (18) to identify the call, followed by the “@” symbol, which in turn is followed by the IP address of the gateway. - The IP address in the
IP address field 317 is the IP address of the gateway (18) in the IP network (26), and the gateway UDP port number in the gatewayUDP port field 318 includes a UDP port identifier identifying a UDP port at which the audio/video path will be terminated at the gateway (18). - It should be noted that throughout the description of the embodiments of this invention, the IP/UDP addresses of all elements such as the gateway (18) will be assumed to be valid IP/UDP addresses directly accessible via the Internet or a private IP network, for example, depending on the specific implementation of the system. As such, it will be assumed, for example, that the gateway (18) will have an IP/UDP address directly accessible by the call controllers and the media relays on their respective nodes, and those addresses will not be obscured by Network Address Translation (NAT) or similar mechanisms. In other words, the IP/UDP information contained in SIP messages (for example the SIP Invite message or the RC Request message which will be described below) will match the IP/UDP addresses of the IP packets carrying these SIP messages.
- It will be appreciated that in many situations, the IP addresses assigned to various elements of the system may be in a private IP address space, and thus not directly accessible from other elements. Furthermore, it will also be appreciated that NAT is commonly used to share a “public” IP address between multiple devices, for example between home PCs and IP telephones sharing a single Internet connection. For example, the gateway (18) may be assigned an IP address such as 192.168.0.5. This address is located in so called “non-routable” (IP) address space and cannot be accessed directly from the Internet. In order for this device to communicate with other computers located on the Internet, the IP address has to be converted into a “public” IP address, for example 24.14.102.5 assigned by the Internet Service Provider, by a device performing NAT, typically a router. In addition to translating the IP address, NAT typically also translates UDP port numbers, for example an audio path originating at the gateway (18) and using a
UDP port 12378 at its private IP address, may have be translated to a UDP port 23465 associated with the public IP address of the NAT device. In other words, when a packet originating from the gateway (18) arrives at an Internet-based node, the source IP/UDP address contained in the IP packet header will be 24.14.102.5:23465, whereas the source IP/UDP address information contained in the SIP message inside this IP packet will be 192.168.0.5:12378. The mismatch in the IP/UDP addresses may cause a problem for SIP-based VoIP systems because, for example, a node will attempt to send messages to a private address but the messages will never get there. - Referring to
FIG. 15 , the call controller (13) includes a processor circuit shown generally at 320. Theprocessor circuit 320 includes amicroprocessor 322,program memory 324, and an I/O port 326. Theprogram memory 324 and the I/O port 326 are in communication with themicroprocessor 322. Theprocessor circuit 320 may include a plurality of microprocessors, a plurality of program memories, and a plurality of I/O ports to be able to handle a large volume of calls. However, for simplicity, theprocessor circuit 320 will be described as having only onemicroprocessor 322,program memory 324, and I/O port 326, it being understood that there may be more. - Generally, the I/
O port 326 includes aninput 328 for receiving messages such as the SIP Invite message from the gateway (18) or from a VoIP telephone (36 inFIG. 1 , for example). The I/O port 326 also has an RCrequest message output 330 for transmitting an RC request message to therouting controller 30 ofFIG. 1 , anRC message input 332 for receiving routing messages from therouting controller 30, agateway output 334 for transmitting messages to thegateway 18 and/or 34 shown inFIG. 1 to advise thegateway 18 and/or 34 to establish an audio path, for example, and agateway input 336 for receiving messages from thegateway 18 and/or 34. The I/O port 326 further includes aSIP output 338 for transmitting messages to the gateway (18 and/or 34) or VoIP telephone (36, for example) to advise thegateway 18 and/or 34 or IP telephone of the IP addresses of the gateways which will establish the audio/video path. The I/O port 326 further includes a voicemail server input andoutput voicemail server 19 shown inFIG. 1 . - While certain inputs and outputs have been shown as separate, it will be appreciated that some may be a single IP address and IP port. For example, the messages sent to the routing controller (30) and received from the routing controller (30) may be transmitted and received on the same single IP port.
- The
program memory 324 includes blocks of code for directing themicroprocessor 322 to carry out various functions of the call controller (13). For example, these blocks of code include afirst block 344 for causing theprocessor circuit 320 to execute a SIP Invite to RC Request process to produce an RC Request Message in response to a received SIP Invite message. In addition, there is a Routing Message to Gateway message block 346 which causes theprocessor circuit 320 of the call controller to produce a gateway query message in response to a received routing message from the routing controller (30). - Referring to
FIGS. 15 and 16 , the SIP Invite to RC Request process is shown in more detail at 344. On receipt of a SIP Invite message of the type shown inFIG. 14 , block 350 directs theprocessor circuit 320 to produce an RC Request Message.Block 352 then directs theprocessor circuit 320 to cause the RC Request Message to be sent to therouting controller 30 illustrated inFIG. 1 . - Referring to
FIG. 17 , an exemplary RC request message is shown generally at 360 and includes acaller identifier field 362, a callee identifier field 364, a digestparameters field 366, and acall identifier field 368. These fields may be populated with the contents of thecaller identifier field 312,callee identifier field 314, digestparameter field 315, and callidentifier field 316 respectively of theSIP Invite message 310 illustrated inFIG. 14 . In other embodiments, the RC request message may further include a type field (not shown) containing a type code to indicate whether the call is from a third party or from a system subscriber. Other variations of an RC request message are explained in PCT Publication No. WO 2008/052340. A type field (not shown) in theRC request message 360 may be advantageous in embodiments where SIP Invite messages may also be received from an IP telephone that is using VoIP software to make a voice call. However, in the embodiments that are illustrated herein, SIP Invite messages originate from the gateway (18), and therefore a type designation is not necessary and may be omitted from theRC request message 360. In embodiments where a SIP Invite message may be received from an IP telephone, the SIP invite to RC request process shown inFIG. 16 may require additional steps, as illustrated inFIG. 5 of PCT Publication No. WO 2008/052340. - As illustrated in
FIG. 8 , theprogram memory 234 includes an RCrequest message handler 380 which directs the routing controller (30) to produce a routing message in response to a received RC request message (360). Referring toFIG. 18A , the RCrequest message handler 380 begins with afirst block 382 that directs the RC processor circuit (230) to separately store the contents of the callee identifier field 364 andcaller identifier field 362 of the RC request message (360) in thecallee identifier store 246 and thecaller identifier store 248 respectively ofFIG. 8 . -
Block 384 then directs the RC processor circuit (230) to use the contents of thecaller username store 249 to locate and retrieve from the database (23) adialing profile 200 associated with the caller, as described above and illustrated inFIG. 9 , for example. The retrieved dialing profile may then be stored in thetemporary memory 240, for example. - The RC
request message handler 380 continues atblock 386, which directs the processor circuit (230) of the routing controller to determine whether the contents of the current number of concurrent calls field 222 of thedialing profile 200 shown inFIG. 9 are less than the contents of the maximum number of concurrent calls field 220 of the dialing profile for the caller and, if so, block 388 directs the processor circuit to increment the contents of the current number ofconcurrent calls field 222 and the processor circuit (230) is directed to point A inFIG. 18B . If the contents of the current number ofconcurrent calls field 222 are equal to or greater than the contents of the maximum number ofconcurrent calls field 220, then block 390 directs the processor circuit (230) to send an error message back to the call controller (13) to cause the call controller to notify the caller that the maximum number of concurrent calls has been reached and no further calls can exist concurrently, including the presently requested call. - Assuming that
block 386 allows the call to proceed, the RC processor circuit (230) is directed to perform certain checks on the callee identifier in thecallee identifier field 246 inFIG. 8 . These checks are shown in greater detail inFIG. 18B . - Referring to
FIG. 18B , the RC processor circuit (230) is directed to afirst block 392 that causes it to determine whether a digit pattern of the callee identifier includes a pattern that matches the contents of the international dialing digits (IDD) field 208 in the dialing profile 200 (shown inFIG. 9 ) associated with the caller. If so, then block 394 directs the RC processor circuit (230) to set a call type code identifier variable maintained by the processor to indicate that the call is an international call, and block 396 directs the processor to produce a reformatted callee identifier by reformatting the callee identifier into a predefined digit format. In this embodiment, this is done by removing the pattern of digits matching the IDD field contents (208) of thecaller dialing profile 200 to effectively shorten the callee identifier. Then, block 398 directs the RC processor circuit (230) to determine whether or not the callee identifier has a length which meets criteria establishing it as a number compliant with the E.164 Standard set by the ITU. If the length does not meet these criteria, then block 400 directs RC processor circuit (230) to send back to the call controller (13) a message indicating the length is not correct. Theprocess 380 is then ended. At thecall controller 13, routines (not shown) stored in theprogram memory 324 may direct the processor circuit (320 ofFIG. 15 ) to respond to the incorrect length message by transmitting a message back to the mobile telephone (12 shown inFIG. 1 ) to indicate that an invalid number has been dialed. - If the length of the amended callee identifier meets the criteria set forth at
block 398, then block 402 directs the RC processor circuit (230) to make a database request to the database (23) to determine whether or not the amended callee identifier is found in the DID field (373) of a record such as shown inFIG. 11 in the DID bank table. If atblock 402 the RC processor circuit (230) receives a response from the database (23) indicating that the reformatted callee identifier produced atblock 396 is found in the DID field (373) of a record in the DID bank table, then the callee is a subscriber to the system and the call is classified as a private network call by directing the processor to block 404, which directs the RC processor circuit (230) to copy the contents of the corresponding username field (371 inFIG. 11 ) from the callee DID bank table record (370 inFIG. 11 ) into the callee identifier store (246 inFIG. 8 ). Thus, the RC processor circuit (230) locates a subscriber username associated with the reformatted callee identifier. The processor (232) is then directed to point B inFIG. 18A . - Referring back to
FIG. 1 , as noted above, thegateway 18 is preferably associated with a pre-determined node, which in the illustrated embodiment is thefirst node 11. Referring back toFIG. 18A , block 406 directs the processor (232 ofFIG. 8 ) to execute a process to determine whether or not the node associated with the reformatted callee identifier in the callee identifier store (246 inFIG. 8 , which, atblock 404, was set to be a username of the callee) is the same node that is associated with thegateway 18 illustrated inFIG. 1 . - To do this, the processor (232) may, for example, identify a node associated with the gateway (18) by using an IP address associated with the gateway to determine a node identifier of the gateway. An IP address associated with the gateway (18) may, for example, be obtained from either the
caller identifier field 362 or thecall identifier field 368 of theRC request message 360 illustrated inFIG. 17 , as each of these fields includes a portion following an “@” symbol that indicates an IP address of the gateway. In order to determine a node identifier associated with the gateway (18) using the IP address associated with gateway (18), the processor 232 (illustrated inFIG. 8 ) may access a gateway node association table stored in the database 23 (illustrated inFIG. 1 ). - Referring to
FIG. 19 , an exemplary gateway node association table is shown generally at 480. The exemplary gateway node association table 480 includes first and second records 482 and 484, each having a respective gatewayIP address field 486 and a respectivenode identifier field 488. It will be appreciated that the exemplary gateway node association table 480 is an example for illustration purposes only. The values in the gateway IP address fields 486 are preferably initialized when a gateway (such as thegateway 18 illustrated inFIG. 1 ) is installed as part of the system (10), and are preferably updated as the IP addresses of the respective gateways may change from time to time. The values in thenode identifier fields 488 are also preferably initialized when a gateway (such as thegateway 18 illustrated inFIG. 1 ) is installed as part of the system (10). - As indicated above, the reformatted callee identifier in the callee identifier store (246 in
FIG. 8 ) was set atblock 404 inFIG. 18B to be a username of the callee from the username field 371 (illustrated inFIG. 11 ), and in this embodiment, a prefix of the username of the callee preferably indicates a node associated with the callee. In the illustrated embodiment, the left-most digit in the username of the callee is a continent code, which is a sufficient prefix to identify a node associated with the callee. However, it will be appreciated that in other embodiments, other prefixes or other information may identify the associated node. Preferably, the values in thenode identifier fields 488 correspond to the prefixes of the usernames in the username fields 371 (illustrated inFIG. 11 ), so that the node associated with the callee is the same node that is associated with thegateway 18 illustrated inFIG. 1 if the prefix of the username of the callee matches the node identifier associated with the gateway (18). Therefore, in the illustrated embodiment, if the reformatted callee identifier in the callee identifier store (246 inFIG. 8 ) is 2001 1050 8667, for example, then in the example ofFIG. 19 , the node associated with the callee is the same node as the node identified by the continent code “2” that is associated with the gateway associated with the IP address 20.14.102.5 in the record 482, but is not the same node as the node identified by the continent code “5” that is associated with the gateway associated with the IP address 104.12.131.12 in the record 484. - Referring back to
FIG. 18A , if atblock 406 the prefix of the username of the callee does not match the node identifier associated with the gateway (18), then the call is a “cross-domain” call, and block 408 inFIG. 18A directs the processor (232 inFIG. 8 ) to set a call type flag in the temporary memory (240 inFIG. 8 ) to indicate the call is a cross-domain call. Then, block 410 ofFIG. 18A directs the processor (232 ofFIG. 8 ) to produce a routing message identifying an address on the private network with which the callee identified by the contents of the callee ID buffer is associated and to set a time to live for the call at a maximum value of 99999, for example. Routing messages and time to live values, and also a method of determining the node in the system with which the callee is associated, are further described in PCT Publication No. WO 2008/052340. Once a routing message is produced atblock 410, block 412 directs the processor (232 inFIG. 8 ) to cause the routing message to be sent to thecall controller 13 shown inFIG. 1 , and the process ends. - Referring back to
FIG. 18B , if atblock 392, the callee identifier stored in the callee identifier store (246 inFIG. 8 ) does not begin with an international dialing digit, then block 414 directs the processor (232) to determine whether or not the callee identifier begins with the same national dial digit code as assigned to the caller. To do this, the processor (232) is directed to refer to the retrieved caller dialing profile as shown inFIG. 9 . InFIG. 9 , the nationaldialing digit code 206 is thenumber 1. Thus, if the callee identifier begins with thenumber 1, then the processor (232) is directed to block 416 inFIG. 18B . -
Block 416 directs the processor (232 ofFIG. 8 ) to examine the callee identifier to determine whether or not the digits following the NDD digit identify an area code that is the same as any of the area codes identified in the local area codes field 212 of thecaller dialing profile 200 shown inFIG. 9 . If not, block 418 ofFIG. 18B directs the processor (232) to set the call type flag to indicate that the call is a national call. If the digits following the NDD digit identify an area code that is the same as a local area code associated with the caller as indicated by the caller dialing profile, block 420 directs the processor (232) to set the call type flag to indicate a local call, national style. After executingblock country code field 210 of the caller dialing profile shown inFIG. 9 . The processor (232) is then directed to block 398 ofFIG. 18B to perform other processing as already described above. - If at
block 414, the callee identifier does not begin with a national dialed digit, block 424 directs the processor (232) to determine whether the callee identifier begins with digits that identify the same area code as the caller. Again, the reference for this is the retrieved caller dialing profile shown inFIG. 9 . The processor (232) determines whether or not the first few digits of the callee identifier identify an area code corresponding to the contents of any area code identifier stored in the local area code field 212 of the retrieved caller dialing profile 200 (illustrated inFIG. 9 ). If so, then block 426 directs the processor (232) to set the call type flag to indicate that the call is a local call. It should be noted that the call will not necessarily be a local call in every case where the first few digits of the callee identifier identify an area code corresponding to the contents of an area code identifier stored in the local area code field 212 (illustrated inFIG. 9 ), and other determinations of when a call is to be considered local may be appropriate. However, it has been found that the determination described above forblock 424 is satisfactory for some purposes. Next, block 428 directs the processor (232) to format the callee identifier into a pre-defined digit format to produce a reformatted callee identifier by prepending the caller country code to the callee identifier, the caller country code being determined from thecountry code field 210 of the retrievedcaller dialing profile 200 shown inFIG. 9 . The processor (232) is then directed to block 398 for further processing as described above. - If at
block 424, the callee identifier does not start with the same area code as the caller, block 430 directs the processor (232 ofFIG. 8 ) to determine whether the number of digits in the callee identifier, i.e. the length of the callee identifier, is within the range of digits indicated by the caller minimum local number length field 214 and the caller maximum local number length field 216 of the retrievedcaller dialing profile 200 shown inFIG. 9 , and whether there is more than one area code identifier stored in the local area code field 212 of the retrieved caller dialing profile. If the number of digits in the callee identifier is within the aforementioned range and there is only one area code identifier stored in the local area code field (212), then block 432 directs the processor (232) to set the call type flag to indicate a local call and block 434 directs the processor (232) to format the callee identifier into a pre-defined digit format to produce a reformatted callee identifier by prepending to the callee identifier the caller country code (as indicated by thecountry code field 210 of the retrievedcaller dialing profile 200 shown inFIG. 9 ) followed by the caller area code as indicated by the local area code stored in the local area code field 212 of thecaller dialing profile 200 shown inFIG. 9 . The processor (232) is then directed to block 398 ofFIG. 18B for further processing as described above. - If at
block 430, the callee identifier has a length that does not fall within the range specified by the caller minimum local number length field (214 inFIG. 9 ) and the caller maximum local number length field (216 inFIG. 9 ), or if there is more than one area code identifier stored in the local area code field 212 of the retrievedcaller dialing profile 200 illustrated inFIG. 9 , then block 436 directs the processor (232) to send an error message back to the call controller (13), and the process ends. - In alternative embodiments, such as those illustrated in PCT Publication No. WO 2008/052340, an additional block (402 in
FIG. 8B of PCT Publication No. WO 2008/052340) may determine whether the callee identifier is a valid username. However, in the embodiment disclosed herein, the callee identifier is assumed to be a telephone number of the callee, and not a username. - From
FIG. 18B , it will be appreciated that there are certain groups of blocks of codes that direct theprocessor 232 inFIG. 8 to determine whether the callee identifier has certain features such as an international dialing digit, a national dialing digit, an area code and a length that meet certain criteria, and cause theprocessor 232 to reformat the callee identifier stored in thecallee identifier store 246 inFIG. 8 , as necessary into a predetermined target format including only a country code, area code, and a normal telephone number, for example, to cause the callee identifier to be compatible with the E.164 number plan standard in this embodiment. This enablesblock 402 inFIG. 18B to have a consistent format of callee identifiers for use in searching through the DIDbank table records 370 of the type shown inFIG. 11 to determine how to route calls to subscribers on the same system. Effectively, therefore blocks 392, 414, 424, and 430 establish call classification criteria for classifying the call as a public network call or a private network call.Block 402 classifies the call, depending on whether or not the formatted callee identifier has a DID bank table record, and this depends on how the call classification criteria are met. - Not all calls will be to subscribers, and this will be detected by the
processor 232 ofFIG. 8 when it executes block 402 inFIG. 18B , and does not find a DID bank table record (370 illustrated inFIG. 11 ) that is associated with the callee, in the DID bank table. When this occurs, the call is classified as a public network call, by directing the processor (232) to point C inFIG. 18C . - Referring to
FIG. 18C , block 438 directs the processor (232) to determine whether the formatted callee identifier in thecallee identifier store 246 inFIG. 8 corresponds to an access code in theaccess code field 173 of a record in the access code association table 170 illustrated inFIG. 10 that is associated with a callee identifier. Because the callee identifier in thecallee identifier store 246 inFIG. 8 has been formatted as described above with reference toFIG. 18B , block 438 may involve determining whether an access code in theaccess code field 173 of a record of the access code association table 170 (illustrated inFIG. 10 ) matches the formatted callee identifier in thecallee identifier store 246 inFIG. 8 , and also whether a callee identifier (as opposed to the “null” value assigned on initialization) is stored in thecallee identifier field 177 in association with the access code. As noted above, for simplicity, this description is directed to embodiments wherein an access code association table 170 associates access codes with respective callee identifiers, caller identifiers, timeout values, and timestamp values, although it will be appreciated that the processes described herein for records in the access code association table 170 may additionally or alternatively be applied to DIDbank table records 370 in an analogous manner. - If at
block 438 the formatted callee identifier in thecallee identifier store 246 inFIG. 8 is the same as an access code in the access code field (173) of a record of the access code association table 170 illustrated inFIG. 10 that is associated with a callee identifier, then block 440 directs the processor (232) to determine whether the caller identifier in the caller identifier store 248 (illustrated inFIG. 8 ) is the same as the caller identifier in the caller identifier field (179) of the record of the access code association table (170), and thus whether the caller identifier in the caller identifier field (179) of the record of the access code association table (170) identifies the mobile telephone identified by the caller identifier in thecaller identifier store 248. If not, then block 442 directs the processor (232) to send an error message to the call controller (13), and the process ends. - But if at
block 440 the caller identifier in the caller identifier store 248 (illustrated inFIG. 8 ) corresponds to the caller identifier in the caller identifier field (179) of the record of the access code association table (170), then the routing controller (30) will produce a routing message that will cause the call controller to establish communication through the IP network (26) to the callee in response to a call received at a channel (20, 22, or 24). Preferably, block 444 includes codes that direct the processor (232) to determine whether the association of the access code with the callee identifier has expired, and thus whether the usability of the access code to initiate a call to the callee has expired, in the manner described above forblock 278 inFIG. 12 . If atblock 444 the association of the access code with the callee identifier has expired, then block 442 directs the processor (232) to send an error message to the call controller (13), and the process ends. Thus the routing controller produces a routing message that causes the call controller to establish the call only when the association of the access code with the callee identifier has not expired. - It will be appreciated that in alternative embodiments, one or more of the caller identifier, timeout, and
timestamp fields FIG. 10 , and in these embodiments, one or more of theblocks - If at
block 444 the association of the access code with the callee identifier has not expired, or if one or both ofblocks callee identifier field 177 of the record of the access code association table (170) in thecallee identifier store 246 illustrated inFIG. 8 . The processor (232) is then directed to point A inFIG. 18B to repeat the steps illustrated inFIG. 18B using the callee identifier retrieved from the callee identifier field (177) in the record of the access code association table (170). - However, if at
block 438 the formatted callee identifier in thecallee identifier store 246 inFIG. 8 does not correspond to an access code in a record of the access code association table 170 illustrated inFIG. 10 that is associated with a callee identifier, then block 448 ofFIG. 18B causes the processor (232) to set the contents of thecallee identifier store 246 ofFIG. 8 to be the newly formatted callee identifier, i.e., a number compatible with the E.164 standard. Then, block 450 ofFIG. 18B directs the processor (232) to generate a routing message identifying a gateway to the public network usable by the call controller (13) to establish a “public system” call. In one embodiment, block 450 includes codes that, for example, direct the processor (232) to search a database of route or master list records and to search a database of supplier records to identify at least one supplier operable to supply a communications link for the call, and to load a routing message buffer with supplier information, time to live values, and timeout values. An example of an implementation of these steps is described with reference toblocks FIGS. 8B and 8D in PCT Publication No. WO 2008/052340. Next, block 452 directs theprocessor 232 ofFIG. 10 to send the routing message to thecall controller 13 inFIG. 1 , and the process ends. - Referring back to
FIG. 18A , if atblock 406, the prefix of the username of the callee matches the node identifier associated with the gateway (18), then the call is on one domain, and block 454 directs the processor (232) to use the callee identifier in thecallee identifier store 246 illustrated inFIG. 8 (which, atblock 404, was set to be a username of the callee) to locate and retrieve a dialing profile for the callee. The dialing profile may be of the type shown inFIG. 9 , for example.Block 456 ofFIG. 18A then directs theprocessor 232 ofFIG. 8 to get call block, call forward, and voicemail records from thedatabase 23 ofFIG. 1 , based on the username identified in the callee dialing profile retrieved by the processor atblock 454. Exemplary call block, call forward, and voicemail records are described in PCT Publication No. WO 2008/052340. - Then block 458 directs the
processor 232 ofFIG. 8 to determine whether or not the caller identifier received in the RC request message matches a block pattern stored in the call block record associated with the callee and retrieved atblock 454. If the caller identifier matches a block pattern, then block 460 directs the processor to send a drop call or non-completion message to the call controller (13) and the process is ended. If the caller identifier does not match a block pattern associated with the callee, then block 462 directs the processor (232) to determine whether or not call forwarding is required, as described in PCT Publication No. WO 2008/052340. - If at
block 462, the call forwarding record for the callee indicates that no call forwarding is required, then the processor (232) is directed to block 464, which directs the processor (232) to generate a routing message identifying an address on the private network, associated with the callee for a “private system” call. In one embodiment, block 464 includes codes that, for example, direct the processor (232) to store, in a routing message buffer, a username and domain of the callee, time to live values, and an IP address of the current node, to determine whether or not the user identified by the callee identifier has paid for voicemail service and if so, to store voicemail information in the routing message buffer. An example of an implementation of these steps is described with reference to blocks 609, 620, 640, 642, and 644 inFIGS. 8A and 8C in PCT Publication No. WO 2008/052340, which is incorporated herein by reference. Next, block 466 directs theprocessor 232 ofFIG. 8 to cause the routing message to be sent to thecall controller 13 inFIG. 1 , and the process ends. - But if at
block 462, the call forwarding record for the callee indicates that call forwarding is required, then block 468 directs the processor (232) to search a dialing profile table to find a dialing profile record as shown inFIG. 9 , for the user identified by the destination number field of the call forward record, as illustrated in PCT Publication No. WO 2008/052340. The processor (232) is further directed to store the username and domain for that user and a time to live value in a routing message buffer, an example of which is described in PCT Publication No. WO 2008/052340. This process is repeated for each call forwarding record associated with the callee identified by thecallee identifier store 246 inFIG. 8 to add to the routing message buffer all call forwarding usernames and domains associated with the callee. - Referring to
FIGS. 1, 18A, and 18C , the routing message sent at one ofblocks call controller 13 and the call controller interprets the receipt of the routing message as a request to establish a call. Referring toFIG. 15 , theprogram memory 324 of thecall controller 13 includes a routing to gateway routine depicted generally at 346. - Where a routing message received at the
call controller 13 is of the type produced atblock 464 shown inFIG. 18A , indicating that the callee is a system subscriber on the same node as the gateway (18) (such as a user of theVoIP telephone 36 illustrated inFIG. 1 ), the routing togateway routine 346 may direct themicroprocessor 322 to cause a message to be sent back through theIP network 26 shown inFIG. 1 to the VoIP telephone (36), using the IP address of the VoIP telephone (36) that is available from the callee username. - Alternatively, if the routing message received at the
call controller 13 is of the type produced atblock 410 shown inFIG. 18A , identifying a domain associated with another node in the system, thecall controller 13 may send a SIP invite message along the high speed/high data throughput link 17 in communication with the other node. The other node may function as explained above and in PCT Publication No. WO 2008/052340, in response to receipt of a SIP invite message. - If the routing message received at the
call controller 13 is of the type produced atblock 450 shown inFIG. 18C , indicating that the callee is not a subscriber to the system (such as a user of thePSTN telephone 32 that is in communication with theIP network 26 through thegateway 34 as illustrated inFIG. 1 ), the call controller sends one or more SIP invite messages to the suppliers identified in the routing message to identify the IP address of a supplier that is able to carry the call, such as the IP address of thegateway 34 illustrated in the example ofFIG. 1 . A process for identifying the IP address of a supplier that is able to carry the call is given in PCT Publication No. WO 2008/052340, which is incorporated herein by reference. In some cases, the gateway of the supplier that is able to carry the call will be thegateway 18 illustrated inFIG. 1 , that is, the same gateway through which the caller telephone (12) initiated the call. For simplicity, the following description assumes that thegateways - Referring to
FIG. 1 , the IP address of thegateway 34 is sent in a message from thecall controller 13 to themedia relay 28, which responds with a message indicating an IP address to which thegateway 18 should send its audio/video traffic, and an IP address to which thegateway 34 should send its audio/video for the call. The call controller conveys the IP address at which themedia relay 28 expects to receive audio/video from thegateways gateways gateway 18 replies to thecall controller 13 with an IP address at which it would like to receive audio/video, and the call controller conveys that IP address to themedia relay 28. The call may then be conducted between the caller and callee through themedia relay 28 and thegateways - If the
call controller 13 receives a routing message of the type produced atblock 464 shown inFIG. 18A , indicating that the callee is a system subscriber on the same node as the gateway (18) (such as a user of theVoIP telephone 36 illustrated inFIG. 1 ), and which has at least one call forwarding number and/or a voicemail number, the call controller attempts to establish a call to thecallee VoIP telephone 36 by seeking from the callee telephone a message indicating an IP address to which themedia relay 28 should send audio/video. If no such message is received from the callee telephone, no call is established. If no call is established within a pre-determined time, thecall controller 13 attempts to establish a call with the next user identified in the call routing message in the same manner. This process is repeated until all call forwarding possibilities have been exhausted, in which case the call controller communicates with thevoicemail server 19 identified in the routing message to obtain an IP address to which themedia relay 28 should send audio/video and the remainder of the process mentioned above for establishing IP addresses at the media relay and the caller telephone is carried out to establish audio/video paths to allowing the caller to leave a voicemail message with the voicemail server. - When an audio/video path through the
media relay 28 is established, a call timer maintained by thecall controller 13 preferably logs the start date and time of the call and logs the call ID and an identification of the route (i.e., audio/video path IP address) for later use in billing. - Referring back to
FIG. 1 , in the event that the caller terminates a call, thegateway 18 sends a SIP bye message to thecall controller 13. Similarly, in the event that the callee terminates the call, thegateway 34 or theVoIP telephone 36 of the callee sends a SIP bye message to thecall controller 13. Exemplary SIP bye messages are described in PCT Publication No. WO 2008/052340. The SIP bye message is received at thecall controller 13, and the call controller executes a process that involves decrementing the contents of the current number of concurrent calls field 222dialing profile 200 of the caller as illustrated inFIG. 9 , generating an RC call stop message (not shown), sending the RC call stop message to therouting controller 30, and sending a “bye” message to the party that did not terminate the call. An exemplary RC call stop message, and an example of how these steps may be implemented, are described in PCT Publication No. WO 2008/052340, which is incorporated herein by reference. - When the
routing controller 30 receives the RC call stop message from thecall controller 13, the routing controller executes an RC call stop message process that involves making various updates to subscriber, reseller, and supplier account records (not shown) following the call. Examples of subscriber, reseller, and supplier account records, and of updates to subscriber, reseller, and supplier account records, are described in PCT Publication No. WO 2008/052340, which is incorporated herein by reference. - While specific embodiments of the invention have been described and illustrated, such embodiments should be considered illustrative of the invention only and not as limiting the invention.
Claims (21)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/135,796 US20210329442A1 (en) | 2008-07-28 | 2020-12-28 | Mobile Gateway |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12989808P | 2008-07-28 | 2008-07-28 | |
PCT/CA2009/001062 WO2010012090A2 (en) | 2008-07-28 | 2009-07-28 | Mobile gateway |
US201113056277A | 2011-01-27 | 2011-01-27 | |
US14/035,806 US10880721B2 (en) | 2008-07-28 | 2013-09-24 | Mobile gateway |
US17/135,796 US20210329442A1 (en) | 2008-07-28 | 2020-12-28 | Mobile Gateway |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/035,806 Continuation US10880721B2 (en) | 2008-07-28 | 2013-09-24 | Mobile gateway |
Publications (1)
Publication Number | Publication Date |
---|---|
US20210329442A1 true US20210329442A1 (en) | 2021-10-21 |
Family
ID=41610774
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/056,277 Active 2030-07-01 US8630234B2 (en) | 2008-07-28 | 2009-07-28 | Mobile gateway |
US14/035,806 Active 2030-12-14 US10880721B2 (en) | 2008-07-28 | 2013-09-24 | Mobile gateway |
US17/135,796 Pending US20210329442A1 (en) | 2008-07-28 | 2020-12-28 | Mobile Gateway |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/056,277 Active 2030-07-01 US8630234B2 (en) | 2008-07-28 | 2009-07-28 | Mobile gateway |
US14/035,806 Active 2030-12-14 US10880721B2 (en) | 2008-07-28 | 2013-09-24 | Mobile gateway |
Country Status (4)
Country | Link |
---|---|
US (3) | US8630234B2 (en) |
EP (1) | EP2311292B1 (en) |
CA (1) | CA2732148C (en) |
WO (1) | WO2010012090A2 (en) |
Families Citing this family (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
BRPI0718312B1 (en) | 2006-11-02 | 2020-05-19 | Digifonica Int Ltd | process for operating a call routing controller, call routing apparatus and data structure |
US8422507B2 (en) | 2006-11-29 | 2013-04-16 | Digifonica (International) Limited | Intercepting voice over IP communications and other data communications |
WO2008116296A1 (en) | 2007-03-26 | 2008-10-02 | Digifonica (International) Limited | Emergency assistance calling for voice over ip communications systems |
US8630234B2 (en) | 2008-07-28 | 2014-01-14 | Digifonica (International) Limited | Mobile gateway |
US8526306B2 (en) * | 2008-12-05 | 2013-09-03 | Cloudshield Technologies, Inc. | Identification of patterns in stateful transactions |
US8848887B2 (en) * | 2009-02-27 | 2014-09-30 | Verizon Patent And Licensing Inc. | Jurisdictionally optimized call routing |
CN101582798B (en) * | 2009-06-19 | 2012-01-11 | 中兴通讯股份有限公司 | Method for remote network management on voice home gateway terminal and system |
BR112012003294B1 (en) * | 2009-08-14 | 2021-06-22 | Telefonaktiebolaget Lm Ericsson (Publ) | METHOD FOR ESTABLISHING A CONNECTION BETWEEN A SOURCE TERMINAL AND A DESTINATION TERMINAL, NETWORK NODE TO A CORE NETWORK, ACCESS CONNECTION POINT OF A CORE NETWORK, HOLDER OF ELECTRONICALLY LEGIBLE DATA, AND, COMPUTING STORAGE MEANS |
PL2478678T3 (en) | 2009-09-17 | 2016-05-31 | Digifonica Int Ltd | Uninterrupted transmission of internet protocol transmissions during endpoint changes |
US8819566B2 (en) | 2010-05-04 | 2014-08-26 | Qwest Communications International Inc. | Integrated multi-modal chat |
US9501802B2 (en) | 2010-05-04 | 2016-11-22 | Qwest Communications International Inc. | Conversation capture |
US9003306B2 (en) | 2010-05-04 | 2015-04-07 | Qwest Communications International Inc. | Doodle-in-chat-context |
US9559869B2 (en) * | 2010-05-04 | 2017-01-31 | Qwest Communications International Inc. | Video call handling |
US9356790B2 (en) | 2010-05-04 | 2016-05-31 | Qwest Communications International Inc. | Multi-user integrated task list |
US20140214687A1 (en) | 2011-07-20 | 2014-07-31 | Horatio Nelson Huxham | Cryptographic expansion device and related protocols |
US8903360B2 (en) * | 2012-05-17 | 2014-12-02 | International Business Machines Corporation | Mobile device validation |
FR3007603A1 (en) * | 2013-06-21 | 2014-12-26 | France Telecom | ESTABLISHING COMMUNICATION BETWEEN A WEB APPLICATION AND A TERMINAL |
US9563438B2 (en) * | 2014-12-16 | 2017-02-07 | International Business Machines Corporation | Mobile computing device reconfiguration in response to environmental factors including consumption of battery power at different rates |
US9584518B1 (en) | 2015-09-09 | 2017-02-28 | Callware Technologies, Inc. | Dynamic communications controller |
WO2017176235A1 (en) * | 2016-04-04 | 2017-10-12 | Hewlett-Packard Development Company, L.P. | Authorization code for a call |
US11212381B2 (en) * | 2020-05-11 | 2021-12-28 | Christopher A. Currie | Methods and systems for short code voice dialing |
US11297469B2 (en) | 2020-08-26 | 2022-04-05 | Stereo App Limited | Complex computing network for generating and handling a waitlist associated with a speaker in an audio conversation on a mobile application |
US11212126B1 (en) | 2020-08-26 | 2021-12-28 | Stereo App Limited | Complex computing network for improving establishment and broadcasting of audio communication among mobile computing devices and for providing rapid audio conversations |
US11317253B2 (en) | 2020-08-26 | 2022-04-26 | Stereo App Limited | Complex computing network for improving establishment and broadcasting of audio communication among mobile computing devices and providing descriptive operator access for improving user experience |
US11864066B2 (en) | 2020-08-26 | 2024-01-02 | Stereo App Limited | Complex computing network for improving establishment and streaming of audio communication among mobile computing devices |
US11212651B1 (en) | 2020-08-26 | 2021-12-28 | Stereo App Limited | Complex computing network for handling audio messages during an audio conversation on a mobile application |
US11290292B2 (en) | 2020-08-26 | 2022-03-29 | Stereo App Limited | Complex computing network for improving streaming of audio conversations and displaying of visual representations on a mobile application |
US11451937B2 (en) | 2020-08-26 | 2022-09-20 | Stereo App Limited | Complex computing network for improving establishment and streaming of audio communication among mobile computing devices |
US12082079B2 (en) | 2020-08-26 | 2024-09-03 | Stereo App Limited | Complex computing network for improving establishment and access of audio communication among mobile computing devices |
US11265685B1 (en) | 2020-08-26 | 2022-03-01 | Stereo App Limited | Complex computing network for establishing audio communication between users on a mobile application |
US11792610B2 (en) | 2020-08-26 | 2023-10-17 | Stereo App Limited | Complex computing network for improving establishment and streaming of audio communication among mobile computing devices |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060034211A1 (en) * | 2004-08-10 | 2006-02-16 | Fujitsu Limited | Communication apparatus, communication control unit, communication method and computer-readable storage medium |
US20070165597A1 (en) * | 2004-06-29 | 2007-07-19 | Damaka, Inc. | System and method for deterministic routing in a peer-to-peer hybrid communications network |
Family Cites Families (468)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4747124A (en) | 1982-09-28 | 1988-05-24 | Opcom | PBX telephone call control system |
US4661974A (en) | 1984-04-13 | 1987-04-28 | At&T Company | Automatic route selection of a private telephone network path on the basis of a public telephone network number |
US4845739A (en) | 1985-07-10 | 1989-07-04 | Fdr Interactive Technologies | Telephonic-interface statistical analysis system |
US4799255A (en) | 1987-01-30 | 1989-01-17 | American Telephone And Telegraph Company - At&T Information Systems | Communication facilities access control arrangement |
JPS63278145A (en) * | 1987-05-11 | 1988-11-15 | Nec Corp | Parameter correspondence check system |
JPH01198770A (en) | 1987-10-16 | 1989-08-10 | Ricoh Co Ltd | Controller for copying machine |
US5726984A (en) | 1989-01-31 | 1998-03-10 | Norand Corporation | Hierarchical data collection network supporting packetized voice communications among wireless terminals and telephones |
US5303297A (en) | 1991-07-25 | 1994-04-12 | Motorola, Inc. | Dynamic pricing method and apparatus for communication systems |
US5265155A (en) | 1991-07-31 | 1993-11-23 | Integrated Communications, Ltd. | Method and apparatus for prepayment of telecommunication connections in a telecommunication switching network |
US5146491A (en) | 1991-08-08 | 1992-09-08 | Pilgrim Telephone, Inc. | Telephone billing method |
US5359642A (en) | 1991-10-30 | 1994-10-25 | International Integrated Communications, Inc. | Method and apparatus for prepayment of telecommunication connections by registered groups of subscribers in a telecommunication switching network |
US5247571A (en) | 1992-02-28 | 1993-09-21 | Bell Atlantic Network Services, Inc. | Area wide centrex |
EP0564669A1 (en) * | 1992-04-04 | 1993-10-13 | Alcatel SEL Aktiengesellschaft | Network of voice and/or fax storage systems |
US5572583A (en) | 1992-04-17 | 1996-11-05 | Bell Atlantic | Advanced intelligent network with intelligent peripherals interfaced to the integrated services control point |
US5325421A (en) | 1992-08-24 | 1994-06-28 | At&T Bell Laboratories | Voice directed communications system platform |
FI96156C (en) * | 1992-11-18 | 1996-05-10 | Nokia Telecommunications Oy | Method and system for establishing a telecommunication connection for telecommunication devices located in a restricted calling area |
US5469497A (en) | 1993-01-19 | 1995-11-21 | Teledebit | Networked interactive call management subsystems with prevention of simultaneous use of a single account number |
US5506893A (en) | 1993-02-19 | 1996-04-09 | At&T Corp. | Telecommunication network arrangement for providing real time access to call records |
US5802502A (en) | 1993-05-24 | 1998-09-01 | British Telecommunications Public Limited Company | System for selective communication connection based on transaction pricing signals |
SE9304119D0 (en) | 1993-12-10 | 1993-12-10 | Ericsson Ge Mobile Communicat | Devices and mobile stations for providing packaged data communication in digital TDMA cellular systems |
JP3299620B2 (en) | 1994-01-21 | 2002-07-08 | 富士通株式会社 | Billing control method |
US5425085C1 (en) | 1994-03-18 | 2001-10-09 | Rates Technology Inc | Least control routing device for separate connection into phone line |
US5519769C1 (en) | 1994-04-04 | 2002-05-28 | Rates Technology Inc | Method and system for updating a call rating database |
US5793762A (en) | 1994-04-12 | 1998-08-11 | U S West Technologies, Inc. | System and method for providing packet data and voice services to mobile subscribers |
US5768521A (en) | 1994-05-16 | 1998-06-16 | Intel Corporation | General purpose metering mechanism for distribution of electronic information |
US5719926A (en) | 1994-06-10 | 1998-02-17 | Communications Product Development, Inc. | Prepaid long-distance telephone service system with flexible operating parameters |
US5559871A (en) | 1994-09-23 | 1996-09-24 | Lucent Technologies Inc. | Call charge control and notification |
US6005926A (en) | 1997-08-29 | 1999-12-21 | Anip, Inc. | Method and system for global communications network management |
US5722067A (en) | 1994-12-23 | 1998-02-24 | Freedom Wireless, Inc. | Security cellular telecommunications system |
US5854975A (en) | 1994-12-23 | 1998-12-29 | Freedom Wireless, Inc. | Prepaid security cellular telecommunications system |
CA2139081C (en) | 1994-12-23 | 1999-02-02 | Alastair Gordon | Unified messaging system and method |
JP2910608B2 (en) | 1995-03-17 | 1999-06-23 | 日本電気株式会社 | Call charge notice system and call charge notice device |
US5677955A (en) | 1995-04-07 | 1997-10-14 | Financial Services Technology Consortium | Electronic funds transfer instruments |
DE69636065T2 (en) | 1995-05-24 | 2006-08-31 | Walker Digital, LLC., Stamford | ACCOUNTING AND COLLECTION SYSTEM FOR 900 NUMBERS AND METHOD FOR ONLINE COMPUTING SERVICES |
US5799072A (en) | 1995-07-21 | 1998-08-25 | Callmanage | Telecommunications call management system |
US5621787A (en) | 1995-09-13 | 1997-04-15 | Bell Atlantic Network Services, Inc. | Prepaid cash card |
US5712907A (en) | 1995-09-18 | 1998-01-27 | Open Port Technology, Inc. | Pro-active message delivery system and method |
US5745556A (en) | 1995-09-22 | 1998-04-28 | At&T Corp. | Interactive and information data services telephone billing system |
US5953504A (en) | 1995-10-10 | 1999-09-14 | Suntek Software Corporation | Public accessible terminal capable of opening an account for allowing access to the internet and E-mail by generating ID code and security code for users |
US5724355A (en) | 1995-10-24 | 1998-03-03 | At&T Corp | Network access to internet and stored multimedia services from a terminal supporting the H.320 protocol |
US5661790A (en) | 1995-11-03 | 1997-08-26 | Ericsson, Inc. | Call back service for a regulatory restrictive area |
IL115967A (en) | 1995-11-12 | 1999-05-09 | Phonet Communication Ltd | Network based distributed pbx system |
US5838682A (en) | 1995-11-28 | 1998-11-17 | Bell Atlantic Network Services, Inc. | Method and apparatus for establishing communications with a remote node on a switched network based on hypertext dialing information received from a packet network |
US5825863A (en) | 1995-12-11 | 1998-10-20 | Walker Asset Management Limited Partnership | Prepaid limited usage calling card |
US5930343A (en) | 1995-12-15 | 1999-07-27 | Lucent Technologies Inc. | Toll call rate provider |
JP3644108B2 (en) | 1995-12-19 | 2005-04-27 | ソニー株式会社 | Call system, connection device, communication terminal device, and call method |
CA2242759C (en) | 1996-01-11 | 2000-10-03 | Bell Communications Research, Inc. | A system and method for processing international telephone numbers |
US5751961A (en) | 1996-01-31 | 1998-05-12 | Bell Communications Research, Inc. | Integrated internet system for translating logical addresses of internet documents to physical addresses using integrated service control point |
US5956391A (en) | 1996-02-09 | 1999-09-21 | Telefonaktiebolaget Lm Ericsson | Billing in the internet |
US6069890A (en) | 1996-06-26 | 2000-05-30 | Bell Atlantic Network Services, Inc. | Internet telephone service |
US5905736A (en) | 1996-04-22 | 1999-05-18 | At&T Corp | Method for the billing of transactions over the internet |
US5883891A (en) | 1996-04-30 | 1999-03-16 | Williams; Wyatt | Method and apparatus for increased quality of voice transmission over the internet |
US5850433A (en) | 1996-05-01 | 1998-12-15 | Sprint Communication Co. L.P. | System and method for providing an on-line directory service |
US6295549B1 (en) | 1996-05-08 | 2001-09-25 | Apple Computer, Inc. | Method and apparatus for listening for incoming calls on multiple port/socket combinations |
US5778187A (en) | 1996-05-09 | 1998-07-07 | Netcast Communications Corp. | Multicasting method and apparatus |
US6141404A (en) | 1996-06-13 | 2000-10-31 | @Track Communications, Inc. | Voice and data communication |
US6021126A (en) | 1996-06-26 | 2000-02-01 | Bell Atlantic Network Services, Inc. | Telecommunication number portability |
US6014379A (en) | 1996-06-26 | 2000-01-11 | Bell Atlantic Network Services, Inc. | Telecommunications custom calling services |
US5970477A (en) | 1996-07-15 | 1999-10-19 | Bellsouth Intellectual Property Management Corporation | Method and system for allocating costs in a distributed computing network |
US6115737A (en) | 1996-07-24 | 2000-09-05 | Telcordia Technologies, Inc. | System and method for accessing customer contact services over a network |
US6005870A (en) | 1996-08-12 | 1999-12-21 | At&T Corp. | Method for called party control of telecommunications network services |
US6594254B1 (en) | 1996-08-16 | 2003-07-15 | Netspeak Corporation | Domain name server architecture for translating telephone number domain names into network protocol addresses |
DE19634664A1 (en) | 1996-08-28 | 1998-03-05 | Sel Alcatel Ag | Method and device for setting a fee in a telecommunications network |
US5845267A (en) | 1996-09-06 | 1998-12-01 | At&T Corp | System and method for billing for transactions conducted over the internet from within an intranet |
US5974043A (en) | 1996-09-16 | 1999-10-26 | Solram Electronics Ltd. | System and method for communicating information using the public switched telephone network and a wide area network |
US5923659A (en) | 1996-09-20 | 1999-07-13 | Bell Atlantic Network Services, Inc. | Telecommunications network |
WO1998015933A2 (en) | 1996-10-07 | 1998-04-16 | Teles Ag Informationstechnologien | Method for transmitting data in a telecommunications network and switch for implementing said method |
US5907547A (en) | 1996-10-24 | 1999-05-25 | At&T Corp | System and method for establishing internet communications links |
US6073013A (en) | 1996-11-04 | 2000-06-06 | Qualcomm Incorporated | Method and apparatus for performing position-based call processing in a mobile telephone system |
CA2218218A1 (en) | 1996-11-08 | 1998-05-08 | At&T Corp. | Promiscuous network monitoring utilizing multicasting within a switch |
US6188752B1 (en) | 1996-11-12 | 2001-02-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for providing prepaid telecommunications services |
US5828740A (en) | 1996-11-14 | 1998-10-27 | Sprint Communications Co., L.P. | Prepaid calling card external/adjunct database processor |
US5867495A (en) | 1996-11-18 | 1999-02-02 | Mci Communications Corporations | System, method and article of manufacture for communications utilizing calling, plans in a hybrid network |
US6754181B1 (en) | 1996-11-18 | 2004-06-22 | Mci Communications Corporation | System and method for a directory service supporting a hybrid communication system architecture |
US5917899A (en) | 1996-12-17 | 1999-06-29 | Ameritech Corporation | Method of connecting a plurality of virtual networks |
US5910946A (en) | 1997-01-13 | 1999-06-08 | Samsung Electronics Co., Ltd. | Wireless internet network architecture for voice and data communications |
US5940598A (en) | 1997-01-28 | 1999-08-17 | Bell Atlantic Network Services, Inc. | Telecommunications network to internetwork universal server |
US6058300A (en) | 1997-02-04 | 2000-05-02 | National Telemanagement Corporation | Prepay telecommunications system |
US6029062A (en) | 1997-02-04 | 2000-02-22 | National Telemanagement Corporation | Prepay telecommunications system with unregistered roaming call processing |
US5875240A (en) | 1997-02-21 | 1999-02-23 | At&T Corp | Method for called party identification and call re-routing |
US6104711A (en) | 1997-03-06 | 2000-08-15 | Bell Atlantic Network Services, Inc. | Enhanced internet domain name server |
US6205135B1 (en) | 1997-03-06 | 2001-03-20 | Lucent Technologies Inc | Access platform for internet-based telephony |
US6137869A (en) | 1997-09-16 | 2000-10-24 | Bell Atlantic Network Services, Inc. | Network session management |
US6785266B2 (en) | 1998-03-02 | 2004-08-31 | Robert Swartz | Internet controlled telephone system |
US6445694B1 (en) | 1997-03-07 | 2002-09-03 | Robert Swartz | Internet controlled telephone system |
US6289010B1 (en) | 1997-03-11 | 2001-09-11 | Bell Atlantic Network Services, Inc. | Inbound gateway authorization processing for inter-carrier internet telephony |
US6721306B1 (en) | 1997-03-11 | 2004-04-13 | Verizon Services Corp. | Public wireless/cordless internet gateway |
US5889774A (en) | 1997-03-14 | 1999-03-30 | Efusion, Inc. | Method and apparatus for selecting an internet/PSTN changeover server for a packet based phone call |
US5909486A (en) | 1997-03-19 | 1999-06-01 | Walker Asset Management Limited Partnership | Method and apparatus for awarding and redeeming prepaid telephone time |
US6870827B1 (en) | 1997-03-19 | 2005-03-22 | Verizon Services Corp. | Voice call alternative routing through PSTN and internet networks |
US6104704A (en) | 1997-03-20 | 2000-08-15 | At&T Corp. | Methods and apparatus for gathering and processing billing information for internet telephony |
US6122357A (en) | 1997-03-28 | 2000-09-19 | Bell Atlantic Network Services, Inc. | Providing enhanced services through double SIV and personal dial tone |
US20010048738A1 (en) | 1997-04-03 | 2001-12-06 | Sbc Technology Resourses, Inc. | Profile management system including user interface for accessing and maintaining profile data of user subscribed telephony services |
US5862202A (en) | 1997-04-10 | 1999-01-19 | Information Medical Retrieval, Inc. | Fax routing system and method using standard fax machine and personal computer |
US6192123B1 (en) | 1997-04-14 | 2001-02-20 | National Tech Team Inc. | Method and apparatus for initiating telephone calls using a data network |
US6597686B1 (en) * | 1997-04-22 | 2003-07-22 | Telcordia Technologies, Inc. | Apparatus and method for internet telephony routing |
US5915093A (en) | 1997-04-24 | 1999-06-22 | Howard Berlin | Computer network debit disk used for prepayment to transfer information from a central computer |
US5915005A (en) | 1997-05-23 | 1999-06-22 | Mci Communications Corporation | Method and system for toll charge and rate inquiry service for portable numbers |
US6298250B1 (en) | 1997-06-19 | 2001-10-02 | Kimberly Nanette Engen | Wireless prepaid telephone system with extended capability |
US6073142A (en) | 1997-06-23 | 2000-06-06 | Park City Group | Automated post office based rule analysis of e-mail messages and other data objects for controlled distribution in network environments |
US6036090A (en) | 1997-07-17 | 2000-03-14 | Telefonaktiebolaget Lm Ericsson | Automated prepayment method for mobile terminals |
WO1999005590A2 (en) | 1997-07-25 | 1999-02-04 | Starvox, Inc. | Apparatus and method for integrated voice gateway |
US5883810A (en) | 1997-09-24 | 1999-03-16 | Microsoft Corporation | Electronic online commerce card with transactionproxy number for online transactions |
US6614765B1 (en) | 1997-10-07 | 2003-09-02 | At&T Corp. | Methods and systems for dynamically managing the routing of information over an integrated global communication network |
CA2276732C (en) | 1997-10-30 | 2007-01-16 | Ntt Mobile Communications Network Inc. | Packet communication network |
US6078647A (en) * | 1997-11-21 | 2000-06-20 | Hewlett Packard Company | Method and apparatus for detecting a data service provider in a public switched telephone network |
US6185565B1 (en) | 1997-12-18 | 2001-02-06 | Nortel Networks Corporation | System and method for communication session disposition responsive to events in a telecommunications network and the internet |
US6636833B1 (en) | 1998-03-25 | 2003-10-21 | Obis Patents Ltd. | Credit card system and method |
US6498791B2 (en) | 1998-04-03 | 2002-12-24 | Vertical Networks, Inc. | Systems and methods for multiple mode voice and data communications using intelligently bridged TDM and packet buses and methods for performing telephony and data functions using the same |
US6173272B1 (en) | 1998-04-27 | 2001-01-09 | The Clearing House Service Company L.L.C. | Electronic funds transfer method and system and bill presentment method and system |
US6324280B2 (en) | 1998-05-05 | 2001-11-27 | Lucent Technologies, Inc. | Optimum routing of calls over the public switched telephone network and the internet |
US6292553B1 (en) | 1998-05-20 | 2001-09-18 | At&T Corp. | Method and apparatus for IP network call delivery |
US8254371B2 (en) | 1998-06-26 | 2012-08-28 | Alcatel Lucent | Method and system for routing and security for telephone calls over a packet-switched network |
US6151385A (en) * | 1998-07-07 | 2000-11-21 | 911 Notify.Com, L.L.C. | System for the automatic notification that a 9-1-1 call has occurred |
US6185414B1 (en) | 1998-07-24 | 2001-02-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Wireless telecommunication system with prepaid architecture |
US6249573B1 (en) | 1998-08-26 | 2001-06-19 | Harris Corporation | Method of time-to-talk calculation |
AU6392899A (en) | 1998-09-15 | 2000-04-03 | Local2Me.Com, Inc. | Dynamic matching TM of users for group communication |
US6839734B1 (en) | 1998-09-21 | 2005-01-04 | Microsoft Corporation | Multimedia communications software with network streaming and multi-format conferencing |
GB2332337B (en) | 1998-09-22 | 2000-05-24 | Cellcom Ltd | Apparatus for generating billing data |
US7212522B1 (en) | 1998-09-30 | 2007-05-01 | Cisco Technology, Inc. | Communicating voice over a packet-switching network |
US6298062B1 (en) | 1998-10-23 | 2001-10-02 | Verizon Laboratories Inc. | System providing integrated services over a computer network |
US6128304A (en) | 1998-10-23 | 2000-10-03 | Gte Laboratories Incorporated | Network presence for a communications system operating over a computer network |
US6240449B1 (en) | 1998-11-02 | 2001-05-29 | Nortel Networks Limited | Method and apparatus for automatic call setup in different network domains |
US7366157B1 (en) | 1998-11-17 | 2008-04-29 | Ericsson Inc. | Methods and system for routing emergency calls through the internet |
US6614781B1 (en) * | 1998-11-20 | 2003-09-02 | Level 3 Communications, Inc. | Voice over data telecommunications network architecture |
US6243689B1 (en) | 1998-12-29 | 2001-06-05 | Robert G. Norton | System and method for authorizing electronic funds transfer at a point of sale |
US6674745B1 (en) * | 1998-12-31 | 2004-01-06 | 3Com Corporation | Method and system for mapping phone numbers to IP addresses |
CA2299037A1 (en) | 1999-02-22 | 2000-08-22 | Peter O. Roach | Method and apparatus for providing quasi-mobile telephone service |
US6775269B1 (en) | 1999-03-30 | 2004-08-10 | Telecom Technologies, Inc. | Method and system for routing telephone calls between a public switched telephone network and an internet protocol network |
US7822188B1 (en) | 1999-04-01 | 2010-10-26 | Callwave, Inc. | Methods and apparatus for providing expanded telecommunications service |
US6609113B1 (en) | 1999-05-03 | 2003-08-19 | The Chase Manhattan Bank | Method and system for processing internet payments using the electronic funds transfer network |
EP1181805A1 (en) | 1999-05-12 | 2002-02-27 | Starvox, Inc. | Method and apparatus for integrated voice gateway with interface to mobile telephone, ip telephone and un-pbx systems |
EP1054569A1 (en) | 1999-05-19 | 2000-11-22 | Alcatel | Method of establishing a connection across a telephone network and an IP network |
US6507644B1 (en) | 1999-06-08 | 2003-01-14 | Worldcom, Inc. | Pre-paid telephone calling card linked to a stored value account |
US7882011B2 (en) | 2000-10-31 | 2011-02-01 | Integral Development Corp. | Systems and methods of conducting financial transactions |
US6650641B1 (en) | 1999-07-02 | 2003-11-18 | Cisco Technology, Inc. | Network address translation using a forwarding agent |
US6449353B1 (en) | 1999-07-13 | 2002-09-10 | Interactive Intelligence, Inc. | Telecommunication number processing technique for a telephony server |
US6804346B1 (en) | 1999-07-13 | 2004-10-12 | Interactive Intelligence, Inc. | Staged predictive dialing system |
US6718032B1 (en) | 1999-07-13 | 2004-04-06 | Interactive Intelligence | Read-only in-memory tables for intelligent call processing system |
AU6346500A (en) | 1999-07-14 | 2001-02-05 | Starvox, Inc. | Method and apparatus for integrating a voice gateway with an ip/pbx telephone system |
US6608831B1 (en) | 1999-07-16 | 2003-08-19 | Cisco Technology, Inc. | Breakout/break-in hybrid network system |
US7644037B1 (en) | 1999-08-16 | 2010-01-05 | Vladimir Ostrovsky | Method and system for transferring electronic funds |
US6553025B1 (en) | 1999-08-18 | 2003-04-22 | At&T Corp. | Multiple routing and automatic network detection of a monitored call from an intercepted targeted IP phone to multiple monitoring locations |
US6560224B1 (en) | 1999-08-18 | 2003-05-06 | At&T Corp. | Automatic IP directory number masking and dynamic packet routing for IP phone surveillance |
US6760324B1 (en) | 1999-09-10 | 2004-07-06 | Array Telecom Corporation | Method, system, and computer program product for providing voice over the internet communication |
US6351464B1 (en) | 1999-09-20 | 2002-02-26 | Mci Worldcom, Inc. | Virtual second line hybrid network communication system |
FR2799326B1 (en) * | 1999-10-04 | 2001-12-28 | France Telecom | PROTOCOL FOR LAUNCHING A REMOTE SOFTWARE APPLICATION AND RESERVATION OF NETWORK RESOURCES WITH QUALITY OF SERVICE |
AU1757201A (en) | 1999-11-05 | 2001-05-14 | American Express Travel Related Services Company, Inc. | Systems and methods for facilitating commercial transactions between parties residing at remote locations |
US6434143B1 (en) | 1999-11-08 | 2002-08-13 | Mci Worldcom, Inc. | Internet protocol telephony voice/video message deposit and retrieval |
US6363065B1 (en) | 1999-11-10 | 2002-03-26 | Quintum Technologies, Inc. | okApparatus for a voice over IP (voIP) telephony gateway and methods for use therein |
US6798767B1 (en) * | 1999-11-16 | 2004-09-28 | Cisco Technology, Inc. | System and method for generating multiple line appearances in a communication network |
US6873599B1 (en) | 1999-12-21 | 2005-03-29 | Lucent Technologies Inc. | Apparatus and method for error isolation in hybrid communications systems |
US6460050B1 (en) | 1999-12-22 | 2002-10-01 | Mark Raymond Pace | Distributed content identification system |
US6707901B1 (en) | 1999-12-27 | 2004-03-16 | Nortel Networks Limited | Subscriber profile extension (SPEX) |
US6937713B1 (en) | 1999-12-30 | 2005-08-30 | At&T Corp. | IP call forward profile |
WO2001050693A1 (en) | 2000-01-05 | 2001-07-12 | Www.Internet Solutions Limited | Messaging system |
US7068668B2 (en) | 2000-01-07 | 2006-06-27 | Feuer Donald S | Method and apparatus for interfacing a public switched telephone network and an internet protocol network for multi-media communication |
US6597783B1 (en) | 2000-02-01 | 2003-07-22 | Cisco Systems, Inc. | System and method for storing, routing, and tracking digital documents in a call center |
US6603977B1 (en) | 2000-02-04 | 2003-08-05 | Sbc Properties, Lp | Location information system for a wireless communication device and method therefor |
US6415018B1 (en) | 2000-02-08 | 2002-07-02 | Lucent Technologies Inc. | Telecommunication system and method for handling special number calls having geographic sensitivity |
WO2001061544A1 (en) | 2000-02-16 | 2001-08-23 | Bea Systems, Inc. | Open market collaboration system for enterprise wide electronic commerce |
US6714793B1 (en) | 2000-03-06 | 2004-03-30 | America Online, Inc. | Method and system for instant messaging across cellular networks and a public data network |
US6766159B2 (en) | 2000-03-10 | 2004-07-20 | Nokia Mobile Phones Ltd. | Alpha tagging and type indication of emergency call number |
US6934279B1 (en) | 2000-03-13 | 2005-08-23 | Nortel Networks Limited | Controlling voice communications over a data network |
US7050426B2 (en) | 2000-03-29 | 2006-05-23 | Edgeaccess, Inc. | Method and system for routing calls from a standard telephone device to a voice over internet protocol network |
US20010052081A1 (en) | 2000-04-07 | 2001-12-13 | Mckibben Bernard R. | Communication network with a service agent element and method for providing surveillance services |
US7006508B2 (en) | 2000-04-07 | 2006-02-28 | Motorola, Inc. | Communication network with a collection gateway and method for providing surveillance services |
GB2361389B (en) | 2000-04-15 | 2004-01-28 | Ericsson Telefon Ab L M | Telecommunications system |
US6574328B1 (en) | 2000-05-04 | 2003-06-03 | Telemaze, Inc. | Telephone call control system for the public switched telephone network |
US7324635B2 (en) | 2000-05-04 | 2008-01-29 | Telemaze Llc | Branch calling and caller ID based call routing telephone features |
US6839323B1 (en) | 2000-05-15 | 2005-01-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Method of monitoring calls in an internet protocol (IP)-based network |
CA2309398C (en) | 2000-05-24 | 2012-02-21 | Steven P. Meyer | A system, computer product and method for providing a private communication portal |
US7359368B1 (en) | 2000-05-25 | 2008-04-15 | Cisco Technology, Inc. | System and method for routing calls using dialing partitions |
US6892184B1 (en) | 2000-06-19 | 2005-05-10 | E4X Inc. | System and method for multiple currency transactions |
US7046658B1 (en) * | 2000-06-23 | 2006-05-16 | At & T Corp. | Method and system for customer selected direct dialed voice-over-internet protocol (VOIP) |
JP4250859B2 (en) | 2000-07-04 | 2009-04-08 | 沖電気工業株式会社 | Communication terminal device and communication interception device |
US6772210B1 (en) | 2000-07-05 | 2004-08-03 | Nortel Networks Limited | Method and apparatus for exchanging communications between telephone number based devices in an internet protocol environment |
US6772188B1 (en) | 2000-07-14 | 2004-08-03 | America Online, Incorporated | Method and apparatus for communicating with an entity automatically identified in an electronic communication |
US7031939B1 (en) | 2000-08-15 | 2006-04-18 | Yahoo! Inc. | Systems and methods for implementing person-to-person money exchange |
GB0022188D0 (en) | 2000-09-11 | 2000-10-25 | Interactive Comm Services Ltd | Voice-over internet protocol |
WO2002025889A2 (en) | 2000-09-19 | 2002-03-28 | Nice Systems Ltd. | Communication management system for computer network based telephones |
US7047561B1 (en) | 2000-09-28 | 2006-05-16 | Nortel Networks Limited | Firewall for real-time internet applications |
EP1362456B1 (en) | 2000-10-10 | 2008-03-19 | Nortel Networks Limited | System and method for intercepting telecommunications |
US20020068545A1 (en) | 2000-11-06 | 2002-06-06 | Johnson Oyama | Method and apparatus for coordinating charging for services provided in a multimedia session |
US6775356B2 (en) | 2000-11-13 | 2004-08-10 | Angelo Salvucci | Real-time incident and response information messaging INA system for the automatic notification that an emergency call has occurred from a telecommunication device |
US7218722B1 (en) | 2000-12-18 | 2007-05-15 | Westell Technologies, Inc. | System and method for providing call management services in a virtual private network using voice or video over internet protocol |
US20020122547A1 (en) | 2000-12-21 | 2002-09-05 | Hinchey Allan J. | Method and apparatus for telephony route selection |
US7554442B2 (en) | 2005-06-17 | 2009-06-30 | Terahop Networks, Inc. | Event-driven mobile hazmat monitoring |
US6748064B2 (en) | 2000-12-28 | 2004-06-08 | Bellsouth Intellectual Property Corporation | Systems and methods for least cost routing of long distance or international telephone calls |
US6674850B2 (en) | 2001-01-09 | 2004-01-06 | Santera Systems Inc. | Call processing digit translation and characterization |
US20020122391A1 (en) * | 2001-01-12 | 2002-09-05 | Shalit Andrew L. | Method and system for providing audio conferencing services to users of on-line text messaging services |
US6944272B1 (en) | 2001-01-16 | 2005-09-13 | Interactive Intelligence, Inc. | Method and system for administering multiple messages over a public switched telephone network |
US6744858B1 (en) * | 2001-01-26 | 2004-06-01 | Telcontrol, Inc. | System and method for supporting multiple call centers |
US7801953B1 (en) | 2001-02-12 | 2010-09-21 | Nortel Networks Limited | Push-to-talk wireless telecommunications system utilizing an voice-over-IP network |
US20020116464A1 (en) | 2001-02-20 | 2002-08-22 | Mak Joon Mun | Electronic communications system and method |
US7055174B1 (en) * | 2001-02-26 | 2006-05-30 | Sprint Spectrum L.P. | Method and system for wiretapping of packet-based communications |
US7120682B1 (en) | 2001-03-08 | 2006-10-10 | Cisco Technology, Inc. | Virtual private networks for voice over networks applications |
EP1244250A1 (en) | 2001-03-21 | 2002-09-25 | Siemens Aktiengesellschaft | Method and telecommunication system for monitoring data streams in a data network |
US6724860B2 (en) * | 2001-03-23 | 2004-04-20 | Siemens Information And Communication Networks, Inc. | Methods and apparatus for transmitting accurate emergency location identification numbers (ELINs) from behind a multi-line telephone system (MLTS) after an emergency caller disconnects |
US6961334B1 (en) | 2001-03-29 | 2005-11-01 | Sonus Networks, Inc. | Intelligence engine |
US7068772B1 (en) | 2001-03-30 | 2006-06-27 | Accessline Communications Corporation | Economical call processing system and method, such as for providing one-number telecommunication services |
US7165052B2 (en) | 2001-03-31 | 2007-01-16 | First Data Corporation | Payment service method and system |
US6954455B1 (en) | 2001-04-02 | 2005-10-11 | At&T Corp. | Technique for providing intelligent features for calls in a communications network independent of network architecture |
US8363647B2 (en) | 2001-04-03 | 2013-01-29 | Voxpath Networks, Inc. | System and method for configuring an IP telephony device |
US7215643B2 (en) * | 2003-07-29 | 2007-05-08 | Level 3 Communications, Llc | System and method for providing alternate routing in a network |
US7593884B2 (en) | 2001-04-10 | 2009-09-22 | Goldman Sachs & Co. | Multi-currency marketplace |
US6907116B2 (en) | 2001-04-25 | 2005-06-14 | Telecommunication Systems Inc. | Time balance based prepaid subscriber database and reporting |
US7620389B2 (en) | 2001-05-16 | 2009-11-17 | Nokia Corporation | Method and system allowing lawful interception of connections such a voice-over-internet protocol calls |
US7899742B2 (en) | 2001-05-29 | 2011-03-01 | American Express Travel Related Services Company, Inc. | System and method for facilitating a subsidiary card account |
US7010727B1 (en) | 2001-06-15 | 2006-03-07 | Nortel Networks Limited | Method and system for negotiating compression techniques to be utilized in packet data communications |
US7996324B2 (en) | 2001-07-10 | 2011-08-09 | American Express Travel Related Services Company, Inc. | Systems and methods for managing multiple accounts on a RF transaction device using secondary identification indicia |
US20030043974A1 (en) | 2001-09-04 | 2003-03-06 | Emerson Harry E. | Stored profile system for storing and exchanging user communications profiles to integrate the internet with the public switched telephone network |
WO2003028355A1 (en) | 2001-09-24 | 2003-04-03 | Fish & Associates, Llp | Automatic routing of telephone calls using a caller id number |
US7076529B2 (en) | 2001-09-27 | 2006-07-11 | Bellsouth Intellectual Property Corporation | Systems and methods for notification of electronic mail receipt in a shared computer environment via advanced intelligent network systems |
US7774711B2 (en) | 2001-09-28 | 2010-08-10 | Aol Inc. | Automatic categorization of entries in a contact list |
US7062222B2 (en) * | 2001-12-17 | 2006-06-13 | Nokia Corporation | Initiating a wireless connection to a broadcast program |
US20030120553A1 (en) | 2001-12-21 | 2003-06-26 | Bell Canada | Method and apparatus for vending and delivering telephone services |
US6947531B1 (en) | 2001-12-27 | 2005-09-20 | Sprint Spectrum L.P. | System and method for advertising supported communications |
US7016343B1 (en) | 2001-12-28 | 2006-03-21 | Cisco Technology, Inc. | PSTN call routing control features applied to a VoIP |
US6726092B2 (en) | 2001-12-28 | 2004-04-27 | Interdigital Technology Corporation | Portable device service payments by multiple means |
US7836160B2 (en) * | 2002-01-08 | 2010-11-16 | Verizon Services Corp. | Methods and apparatus for wiretapping IP-based telephone lines |
US7277528B2 (en) | 2002-02-12 | 2007-10-02 | Siemens Information And Communication Networks, Inc.- Boca Raton | Call-content determinative selection of interception access points in a soft switch controlled network |
US7062253B2 (en) | 2002-04-10 | 2006-06-13 | Sprint Spectrum L.P. | Method and system for real-time tiered rating of communication services |
US7142664B2 (en) | 2002-05-06 | 2006-11-28 | Avaya Technology Corp. | Intelligent multimode message alerts |
US7127241B2 (en) | 2002-05-09 | 2006-10-24 | Casabyte, Inc. | Method, apparatus and article to remotely associate wireless communications devices with subscriber identities and/or proxy wireless communications devices |
US7412049B1 (en) | 2002-05-31 | 2008-08-12 | At&T Delaware Intellectual Property, Inc. | System and method for real-time blocking of a telephone call |
US7177311B1 (en) | 2002-06-04 | 2007-02-13 | Fortinet, Inc. | System and method for routing traffic through a virtual router-based network switch |
AU2002317425A1 (en) | 2002-07-16 | 2004-02-02 | Nokia Corporation | Optimized routing between communication networks |
US20040019539A1 (en) | 2002-07-25 | 2004-01-29 | 3Com Corporation | Prepaid billing system for wireless data networks |
ATE281734T1 (en) | 2002-08-08 | 2004-11-15 | Cit Alcatel | LEGAL INTERCEPTION FOR VOIP CALLS IN AN IP COMMUNICATION NETWORK |
US8166533B2 (en) | 2002-08-17 | 2012-04-24 | Rockstar Bidco Lp | Method for providing media communication across firewalls |
US7676215B2 (en) | 2002-10-16 | 2010-03-09 | Alcatel Lucent Usa Inc. | Emergency call back method |
US6963739B2 (en) | 2002-10-21 | 2005-11-08 | Motorola, Inc. | Method and apparatus for providing information intercept in an ad-hoc wireless network |
US7539086B2 (en) * | 2002-10-23 | 2009-05-26 | J2 Global Communications, Inc. | System and method for the secure, real-time, high accuracy conversion of general-quality speech into text |
US7330835B2 (en) | 2002-10-31 | 2008-02-12 | Federal Reserve Bank Of Minneapolis | Method and system for tracking and reporting automated clearing house transaction status |
US7454200B2 (en) | 2002-11-13 | 2008-11-18 | Lucent Technologies Inc. | Personal handyphone system component employment of prepay telephone service system component to allow user employment of wireless telephone service subsequent to purchase thereof |
EP1437693A1 (en) | 2003-01-08 | 2004-07-14 | Itsmobile Limited | A mobile telecommunications billing routing system and method |
JP4270888B2 (en) | 2003-01-14 | 2009-06-03 | パナソニック株式会社 | Service and address management method in WLAN interconnection |
US7003493B2 (en) | 2003-01-22 | 2006-02-21 | First Data Corporation | Direct payment with token |
US7457865B2 (en) | 2003-01-23 | 2008-11-25 | Redknee Inc. | Method for implementing an internet protocol (IP) charging and rating middleware platform and gateway system |
US7797459B1 (en) | 2003-02-11 | 2010-09-14 | At&T Intellectual Property Ii, L.P. | Access independent common architecture for real-time communications services for networking environments |
US20040165709A1 (en) | 2003-02-24 | 2004-08-26 | Pence Robert Leslie | Stealth interception of calls within a VoIP network |
US7664056B2 (en) | 2003-03-10 | 2010-02-16 | Meetrix Corporation | Media based collaboration using mixed-mode PSTN and internet networks |
WO2004102941A1 (en) | 2003-03-21 | 2004-11-25 | Easylink Networks Inc. | System and process for routing telephony communications from a conventional telephone set through a data network |
US6963557B2 (en) * | 2003-03-29 | 2005-11-08 | Intrado Inc. | System and method for routing telephone calls involving internet protocol network |
ATE546955T1 (en) * | 2003-04-09 | 2012-03-15 | Ericsson Telefon Ab L M | LEGAL INTERCEPTION OF MULTIMEDIA CONNECTIONS |
US20040218748A1 (en) | 2003-04-30 | 2004-11-04 | Stephen Fisher | Method and system for providing and using telephone call routing rules |
US7454510B2 (en) | 2003-05-29 | 2008-11-18 | Microsoft Corporation | Controlled relay of media streams across network perimeters |
US7436835B2 (en) * | 2003-05-30 | 2008-10-14 | Lucent Technologies Inc. | Forced bearer routing for packet-mode interception |
US7110523B2 (en) | 2003-05-30 | 2006-09-19 | Interactive Intelligence, Inc. | System and method for distributing and routing calls in a call center |
US7447909B2 (en) | 2003-06-05 | 2008-11-04 | Nortel Networks Limited | Method and system for lawful interception of packet switched network services |
US7440441B2 (en) | 2003-06-16 | 2008-10-21 | Redknee Inc. | Method and system for Multimedia Messaging Service (MMS) rating and billing |
US7620808B2 (en) | 2003-06-19 | 2009-11-17 | Nokia Corporation | Security of a communication system |
US7627091B2 (en) | 2003-06-25 | 2009-12-01 | Avaya Inc. | Universal emergency number ELIN based on network address ranges |
US6932268B1 (en) | 2003-06-30 | 2005-08-23 | Checkfree Corporation | Dual mode credit card based payment technique |
EP1661367B1 (en) | 2003-07-11 | 2013-08-21 | Computer Associates Think, Inc. | Packet sniffer |
EP1507395A1 (en) | 2003-08-14 | 2005-02-16 | Siemens Aktiengesellschaft | Method for the setting up of call forwarding for a SIP telephone number of a SIP client in a mixed circuit switched / packet network |
US7042985B1 (en) | 2003-08-27 | 2006-05-09 | Bellsouth Intellectual Property Corporation | Method, system and computer program product for providing a regional E911 network |
US7477843B1 (en) | 2003-09-05 | 2009-01-13 | Nortel Networks Limited | Method of and system for routing in a photonic network |
DE60327562D1 (en) | 2003-09-05 | 2009-06-18 | Ericsson Telefon Ab L M | MONITORING IN A TELECOMMUNICATIONS NETWORK |
US7027564B2 (en) | 2003-09-22 | 2006-04-11 | Foundry Networks, Inc. | System, method and apparatus for supporting E911 emergency services in a data communications network |
CA2483123A1 (en) | 2003-09-30 | 2005-03-30 | At&T Corp. | Enhanced call notification service |
US7486684B2 (en) | 2003-09-30 | 2009-02-03 | Alcatel-Lucent Usa Inc. | Method and apparatus for establishment and management of voice-over IP virtual private networks in IP-based communication systems |
US8543477B2 (en) | 2003-09-30 | 2013-09-24 | Federal Reserve Bank Of Atlanta | Value tracking and reporting of automated clearing house transactions |
US7440442B2 (en) | 2003-10-21 | 2008-10-21 | 3Com Corporation | IP-based enhanced emergency services using intelligent client devices |
US7715413B2 (en) | 2003-10-23 | 2010-05-11 | Emerj, Inc. | Multi-network exchange system for telephony applications |
EP1528774A1 (en) | 2003-10-30 | 2005-05-04 | Alcatel | Method and system of providing lawful interception of calls |
US7203478B2 (en) | 2003-12-08 | 2007-04-10 | Lucent Technologies Inc. | Network support for mobile service plan minute exchange by category |
US20050135401A1 (en) | 2003-12-18 | 2005-06-23 | Michael Schmidt | Multicast message routing systems and methods |
US7765263B1 (en) | 2003-12-19 | 2010-07-27 | Apple Inc. | Method and apparatus for processing electronic messages |
US8078164B2 (en) | 2004-01-06 | 2011-12-13 | Vasu Networks Corporation | Mobile telephone VOIP/cellular seamless roaming switching controller |
US8554876B2 (en) | 2004-01-23 | 2013-10-08 | Hewlett-Packard Development Company, L.P. | User profile service |
US7346156B1 (en) | 2004-01-29 | 2008-03-18 | Stanacard Llc | Methods and apparatuses for placing a telephone call |
US20050169248A1 (en) | 2004-02-04 | 2005-08-04 | Nortel Networks Limited | Method and apparatus for providing in-band location information in an emergency response network |
US7386111B2 (en) | 2004-02-10 | 2008-06-10 | Vonage Network Inc. | Method and apparatus for placing a long distance call based on a virtual phone number |
US20050192897A1 (en) | 2004-02-10 | 2005-09-01 | First Data Corporation | Methods and systems for payment-network enrollment |
US7587757B2 (en) | 2004-02-11 | 2009-09-08 | Texas Instruments Incorporated | Surveillance implementation in managed VOP networks |
US8594298B2 (en) | 2004-02-20 | 2013-11-26 | Avaya Inc. | Call management |
US7177399B2 (en) | 2004-02-27 | 2007-02-13 | Nortel Network Limited | Determining the geographical location from which an emergency call originates in a packet-based communications network |
US7574736B2 (en) | 2004-03-03 | 2009-08-11 | Microsoft Corporation | System and method for efficiently transferring media across firewalls |
US7702308B2 (en) | 2004-03-11 | 2010-04-20 | Alcatel-Lucent Usa Inc. | Method of associating data with a call to a call center |
US7738384B2 (en) | 2004-03-23 | 2010-06-15 | Level 3 Communications, Llc | Systems and methods for accessing voice transmissions |
US20050222952A1 (en) | 2004-03-31 | 2005-10-06 | Dave Garrett | System and method for real-time account validation for an on-line payment system |
US7616753B2 (en) | 2004-05-03 | 2009-11-10 | Sprint Communications Company L.P. | System and method for providing intercept of international calls to reroute the call from the default international routing |
US8145182B2 (en) | 2004-05-07 | 2012-03-27 | Interdigital Technology Corporation | Supporting emergency calls on a wireless local area network |
US7174156B1 (en) | 2004-05-10 | 2007-02-06 | Sprint Spectrum L.P. | Method and system for tracking and billing vocoder bypass calls in a wireless wide area network |
US7764944B2 (en) | 2004-06-24 | 2010-07-27 | Alcatel-Lucent Usa Inc. | Method of providing a unique call back number for wireless 9-1-1 calls |
US8016185B2 (en) | 2004-07-06 | 2011-09-13 | Visa International Service Association | Money transfer service with authentication |
US7437665B2 (en) | 2004-07-23 | 2008-10-14 | International Business Machines Corporation | SEF parser and EDI parser generator |
US7089012B2 (en) | 2004-07-29 | 2006-08-08 | Motorola, Inc. | Method and system for use in reducing cost associated with lost connections in wireless communication |
US7706401B2 (en) | 2004-08-13 | 2010-04-27 | Verizon Business Global Llc | Method and system for providing interdomain traversal in support of packetized voice transmissions |
EP1805718B1 (en) | 2004-08-19 | 2009-10-07 | Miroslav Marc | Wireless toll collection system |
JP4851458B2 (en) | 2004-09-14 | 2012-01-11 | コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ | Apparatus, oscillation stage, frequency selector, system, method |
US7580886B1 (en) | 2004-09-15 | 2009-08-25 | Federal Reserve Bank Of Atlanta | Managing foreign payments in an international ACH |
US8116307B1 (en) * | 2004-09-23 | 2012-02-14 | Juniper Networks, Inc. | Packet structure for mirrored traffic flow |
US20060072547A1 (en) | 2004-09-29 | 2006-04-06 | Lucent Technologies Inc. | Systems and methods for serving VolP emergency calls |
US7643822B2 (en) | 2004-09-30 | 2010-01-05 | Google Inc. | Method and system for processing queries initiated by users of mobile devices |
US7764768B2 (en) * | 2004-10-06 | 2010-07-27 | Alcatel-Lucent Usa Inc. | Providing CALEA/legal intercept information to law enforcement agencies for internet protocol multimedia subsystems (IMS) |
US7573982B2 (en) | 2004-10-12 | 2009-08-11 | Bellsouth Intellectual Property Corporation | Methods and systems for managing a call session |
WO2006045102A2 (en) * | 2004-10-20 | 2006-04-27 | Seven Networks, Inc. | Method and apparatus for intercepting events in a communication system |
EP1808010A2 (en) | 2004-10-25 | 2007-07-18 | Intrado, Inc. | System and method for unilateral verification of caller location information |
US20060095320A1 (en) | 2004-11-03 | 2006-05-04 | Jones Lisa S | System and method of electronic advertisement and commerce |
US7190959B2 (en) | 2004-11-19 | 2007-03-13 | Tekelec | Methods and systems for signaling in a communications network for ported, migrated and/or dual-mode subscribers |
US8824655B2 (en) | 2004-11-23 | 2014-09-02 | Transera Communications, Inc. | Routing inbound communications across call centers and the like |
US8682919B1 (en) | 2004-12-23 | 2014-03-25 | Google Inc. | System and method for navigating related data |
FI20041659A0 (en) | 2004-12-23 | 2004-12-23 | Nokia Corp | Method of routing communications to a VoIP terminal in a mobile communication system |
US7593390B2 (en) | 2004-12-30 | 2009-09-22 | Intel Corporation | Distributed voice network |
JP2006191474A (en) * | 2005-01-07 | 2006-07-20 | Oki Electric Ind Co Ltd | Emergency reporting system |
US7738915B2 (en) | 2005-01-14 | 2010-06-15 | Nextel Communications Inc. | System and method for private wireless networks |
US8856359B2 (en) * | 2005-06-29 | 2014-10-07 | Qualcomm Connected Experiences, Inc. | Caller-callee association of a plurality of networked devices |
NZ537800A (en) | 2005-01-20 | 2007-03-30 | Colin Lawrence Melvin Baker | Global telephone number |
US8718258B2 (en) | 2005-01-24 | 2014-05-06 | Sprint Communication Company L.P. | System and method for jurisdictional routing |
US20060195398A1 (en) | 2005-02-04 | 2006-08-31 | Sanjeev Dheer | Method and apparatus for processing payment requests |
US7715821B2 (en) | 2005-02-18 | 2010-05-11 | Alcatel-Lucent Usa Inc. | Method of updating a unique call back number for a wireless emergency call |
US7565131B2 (en) | 2005-03-08 | 2009-07-21 | Alcatel-Lucent Usa Inc. | Emergency call back through intersystem paging |
US20060235758A1 (en) | 2005-04-08 | 2006-10-19 | Paypal Inc. | Authorization techniques |
US7496182B2 (en) | 2005-04-15 | 2009-02-24 | Verizon Business Global Llc | Handling emergency service calls originating from internet telephony |
US7664495B1 (en) | 2005-04-21 | 2010-02-16 | At&T Mobility Ii Llc | Voice call redirection for enterprise hosted dual mode service |
GB2425679A (en) | 2005-04-27 | 2006-11-01 | Hewlett Packard Development Co | Scanning computing entities for vulnerabilities |
US20060258328A1 (en) * | 2005-05-10 | 2006-11-16 | Lucent Technologies Inc. | User defined codes for emergency calls |
US7545761B1 (en) | 2005-06-08 | 2009-06-09 | Cellco Partnership | Session classification for differentiated prepaid accounting |
US8750290B2 (en) | 2005-06-10 | 2014-06-10 | Zoom Telephonics, Inc. | Method and apparatus for ensuring accessibility to emergency service via VoIP or via PSTN |
US20060281437A1 (en) | 2005-06-13 | 2006-12-14 | Qwest Communications International Inc. | Systems and methods for supporting E911 emergency services in a data communications network |
CN101218785B (en) | 2005-07-01 | 2010-06-16 | 艾利森电话股份有限公司 | Monitoring method and apparatus in telecommunication system |
GB0515123D0 (en) * | 2005-07-22 | 2005-08-31 | M M I Res Ltd | Method of compiling a list of identifiers associated with a mobile device user |
US7975037B2 (en) | 2005-07-29 | 2011-07-05 | Verizon Patent And Licensing Inc. | Policy engine in an Internet Protocol multimedia subsystem |
US20070036139A1 (en) | 2005-08-09 | 2007-02-15 | Ashish Patel | System and method for authenticating internetwork resource requests |
JP4457058B2 (en) | 2005-08-26 | 2010-04-28 | アラクサラネットワークス株式会社 | Packet transfer device with filtering |
US7916846B1 (en) | 2005-08-31 | 2011-03-29 | At&T Intellectual Property Ii, L.P. | System and method for identifying and treating calls |
US8166547B2 (en) | 2005-09-06 | 2012-04-24 | Fortinet, Inc. | Method, apparatus, signals, and medium for managing a transfer of data in a data network |
US20070064919A1 (en) | 2005-09-14 | 2007-03-22 | Zoneson Chen | Communication method for placing phone calls by using a fixed dial plan |
US7817608B2 (en) | 2005-09-23 | 2010-10-19 | Widevine Technologies, Inc. | Transitioning to secure IP communications for encoding, encapsulating, and encrypting data |
US7907551B2 (en) | 2005-10-06 | 2011-03-15 | Telecommunication Systems, Inc. | Voice over internet protocol (VoIP) location based 911 conferencing |
WO2007044454A2 (en) | 2005-10-06 | 2007-04-19 | Telecommunication Systems, Inc. | Voice over internet protocol (voip) location based 911 conferencing |
US8200575B2 (en) | 2005-10-11 | 2012-06-12 | Raul Armando Cordero Torres | Secure electronic payment system and methods |
US7907713B2 (en) * | 2005-10-25 | 2011-03-15 | Tekelec | Methods, systems, and computer program products for using a presence database to deliver enhanced presence information regarding communications made to or from a presentity |
WO2007056158A2 (en) * | 2005-11-03 | 2007-05-18 | Roamware, Inc. | Network-based system for rerouting phone calls from phone networks to voip clients for roamers and subscribers who do not answer |
US7907718B2 (en) | 2005-11-18 | 2011-03-15 | Cisco Technology, Inc. | VoIP call routing |
US7639792B2 (en) | 2005-11-23 | 2009-12-29 | Att Knowledge Ventures, L.P. | System and method for location management and emergency support for a voice over internet protocol device |
US20070121866A1 (en) | 2005-11-28 | 2007-05-31 | Nokia Corporation | Method, system and corresponding program products and devices for VoIP-communication |
US7599944B2 (en) | 2005-12-16 | 2009-10-06 | Microsoft Corporation | Electronic data interchange (EDI) schema simplification interface |
US7447707B2 (en) | 2005-12-16 | 2008-11-04 | Microsoft Corporation | Automatic schema discovery for electronic data interchange (EDI) at runtime |
US7647500B2 (en) | 2005-12-16 | 2010-01-12 | Microsoft Corporation | Synchronous validation and acknowledgment of electronic data interchange (EDI) |
US20090017842A1 (en) * | 2006-01-12 | 2009-01-15 | Masaki Fukasaku | Mobile Communication System, Telephone Calling Method and Program Software for The Same |
US8024785B2 (en) | 2006-01-16 | 2011-09-20 | International Business Machines Corporation | Method and data processing system for intercepting communication between a client and a service |
WO2007087077A2 (en) | 2006-01-17 | 2007-08-02 | Medical Envelope L.L.C. | System and method for providing medical and contact information during an emergency call |
CN101496387B (en) | 2006-03-06 | 2012-09-05 | 思科技术公司 | System and method for access authentication in a mobile wireless network |
US7657011B1 (en) | 2006-03-16 | 2010-02-02 | Juniper Networks, Inc. | Lawful intercept trigger support within service provider networks |
US7706779B2 (en) | 2006-03-16 | 2010-04-27 | Research In Motion Limited | System and method for controlling VCC functionality in a network environment including IMS |
US8036362B1 (en) | 2006-03-17 | 2011-10-11 | RNK Inc. | Communication system and call forwarding management |
CA2659007C (en) | 2006-03-20 | 2015-06-16 | Google Inc. | Synchronous message management system |
US8768951B2 (en) | 2006-03-20 | 2014-07-01 | Bce Inc. | Method for populating a location information database used in the delivery of emergency and other location-based services in a VoIP environment |
JP2007295541A (en) * | 2006-03-28 | 2007-11-08 | Matsushita Electric Ind Co Ltd | Wireless communication system |
US8763081B2 (en) | 2006-04-03 | 2014-06-24 | Bridgeport Networks, Inc. | Network based authentication |
US8228897B2 (en) | 2006-04-04 | 2012-07-24 | Telecommunication Systems, Inc. | SS7 ANSI-41 to SIP based call signaling conversion gateway for wireless VoIP E911 |
WO2007125530A2 (en) | 2006-04-27 | 2007-11-08 | D.S.P. Group Ltd. | Routing path optimization between si p endpoints according to nat topology |
US7929955B1 (en) | 2006-04-28 | 2011-04-19 | At&T Mobility Ii Llc | Managing multiple CLI identities |
US9252981B2 (en) * | 2006-06-13 | 2016-02-02 | At&T Intellectual Property I, L.P. | Method and apparatus for processing a communication request from a roaming voice over IP terminal |
US8050273B2 (en) | 2006-06-22 | 2011-11-01 | Alcatel Lucent | Lawful interception in IP networks |
US7940896B2 (en) | 2006-06-29 | 2011-05-10 | Avaya Inc. | Adaption of emergency calls to the emergency services network based on caller location |
US8417791B1 (en) | 2006-06-30 | 2013-04-09 | Google Inc. | Hosted calling service |
US7680737B2 (en) | 2006-07-06 | 2010-03-16 | Moneygram International, Inc. | Systems and methods for processing payments with payment review features |
US9014197B2 (en) | 2006-07-14 | 2015-04-21 | Verizon Patent And Licensing Inc. | E911 implementation for IP phones |
US8036366B2 (en) | 2006-08-04 | 2011-10-11 | Microsoft Corporation | Intelligent formatting of VoIP telephone numbers |
CA2598200C (en) | 2006-08-21 | 2015-10-27 | Connexon Telecom Inc. | System and method for delivering callback numbers for emergency calls in a voip system |
US8774370B2 (en) | 2006-08-21 | 2014-07-08 | Connexon Telecom Inc. | System and method for delivering callback numbers for emergency calls in a VOIP system |
US8306063B2 (en) | 2006-08-29 | 2012-11-06 | EXFO Services Assurance, Inc. | Real-time transport protocol stream detection system and method |
US9432830B2 (en) | 2006-08-29 | 2016-08-30 | Nokia Technologies Oy | Method of advertising using mobile communications |
US7676229B2 (en) * | 2006-08-31 | 2010-03-09 | Syniverse Technologies, Inc. | Cellular-to-VoIP call establishment systems, methods, devices, and computer software |
US8161078B2 (en) | 2006-09-20 | 2012-04-17 | Microsoft Corporation | Electronic data interchange (EDI) data dictionary management and versioning system |
ITMI20061886A1 (en) * | 2006-10-02 | 2008-04-03 | Ericsson Telefon Ab L M | PROCEDURE AND ARCHITECTURE OF LEGAL INTERCEPTION IN BROADBAND NETWORKS |
BRPI0718312B1 (en) | 2006-11-02 | 2020-05-19 | Digifonica Int Ltd | process for operating a call routing controller, call routing apparatus and data structure |
US7983691B1 (en) | 2006-11-06 | 2011-07-19 | Google Inc. | Geographically localizing mobile communciation devices |
US8422507B2 (en) | 2006-11-29 | 2013-04-16 | Digifonica (International) Limited | Intercepting voice over IP communications and other data communications |
US9571303B2 (en) | 2006-12-19 | 2017-02-14 | Bce Inc. | Method, system and apparatus for handling a request for a media-over-packet communication session |
US8599747B1 (en) | 2006-12-20 | 2013-12-03 | Radisys Canada Inc. | Lawful interception of real time packet data |
US8010079B2 (en) * | 2006-12-28 | 2011-08-30 | Trueposition, Inc. | Emergency wireless location system including a wireless transceiver |
WO2008085614A2 (en) | 2007-01-08 | 2008-07-17 | Iskoot, Inc. | Methods and systems of providing mobile device calling features |
US8427981B2 (en) | 2007-02-23 | 2013-04-23 | Interactive Intelligence, Inc. | System and method for recording and monitoring communications using a media server |
WO2008116296A1 (en) | 2007-03-26 | 2008-10-02 | Digifonica (International) Limited | Emergency assistance calling for voice over ip communications systems |
US8627211B2 (en) | 2007-03-30 | 2014-01-07 | Uranus International Limited | Method, apparatus, system, medium, and signals for supporting pointer display in a multiple-party communication |
US7765261B2 (en) | 2007-03-30 | 2010-07-27 | Uranus International Limited | Method, apparatus, system, medium and signals for supporting a multiple-party communication on a plurality of computer servers |
US8702505B2 (en) | 2007-03-30 | 2014-04-22 | Uranus International Limited | Method, apparatus, system, medium, and signals for supporting game piece movement in a multiple-party communication |
US8060887B2 (en) | 2007-03-30 | 2011-11-15 | Uranus International Limited | Method, apparatus, system, and medium for supporting multiple-party communications |
US7765266B2 (en) | 2007-03-30 | 2010-07-27 | Uranus International Limited | Method, apparatus, system, medium, and signals for publishing content created during a communication |
US7950046B2 (en) * | 2007-03-30 | 2011-05-24 | Uranus International Limited | Method, apparatus, system, medium, and signals for intercepting a multiple-party communication |
US8756659B2 (en) * | 2007-04-19 | 2014-06-17 | At&T Intellectual Property I, L.P. | Access authorization servers, methods and computer program products employing wireless terminal location |
US7978620B2 (en) | 2007-05-14 | 2011-07-12 | Cisco Technology, Inc. | Dynamically troubleshooting voice quality |
US9185216B2 (en) | 2007-06-15 | 2015-11-10 | Blackberry Limited | System and method for indicating emergency call back to user equipment |
US20090135735A1 (en) | 2007-11-27 | 2009-05-28 | Tellabs Operations, Inc. | Method and apparatus of RTP control protocol (RTCP) processing in real-time transport protocol (RTP) intermediate systems |
US20090135724A1 (en) | 2007-11-27 | 2009-05-28 | Tellabs Operations, Inc. | Method and apparatus of RTP control protocol (RTCP) processing in real-time transport protocol (RTP) intermediate systems |
US8514841B2 (en) | 2007-11-30 | 2013-08-20 | Broadsoft, Inc. | IP-based call content intercept using repeaters |
US8244204B1 (en) | 2007-12-11 | 2012-08-14 | Cellco Partnership | Timed override of incoming call restrictions to facilitate callback after an emergency call |
US8472431B2 (en) | 2008-01-24 | 2013-06-25 | At&T Intellectual Property I, L.P. | System and method of providing IMS services to users on terminating non IMS devices |
EP2243286B1 (en) | 2008-02-14 | 2013-11-06 | Telefonaktiebolaget L M Ericsson (PUBL) | Lawful interception of non-local subscribers |
US8300632B2 (en) | 2008-02-21 | 2012-10-30 | Avaya Inc. | System and method for distributed call monitoring/recording using the session initiation protocol (SIP) |
US8910272B2 (en) | 2008-02-28 | 2014-12-09 | Hob Gmbh & Co. Kg | Computer communication system for communication via public networks |
US20090238168A1 (en) | 2008-03-18 | 2009-09-24 | Paraxip Technologies Inc. | Communication node and method for handling sip communication |
EP3484135A1 (en) | 2008-04-02 | 2019-05-15 | Twilio Inc. | System and method for processing telephony sessions |
US8219115B1 (en) | 2008-05-12 | 2012-07-10 | Google Inc. | Location based reminders |
US8165090B2 (en) | 2008-05-15 | 2012-04-24 | Nix John A | Efficient handover of media communications in heterogeneous IP networks |
CN101621506A (en) | 2008-07-01 | 2010-01-06 | 鸿富锦精密工业(深圳)有限公司 | Method for realizing real-time multi-media bidirectional communication by NAT |
US8630234B2 (en) | 2008-07-28 | 2014-01-14 | Digifonica (International) Limited | Mobile gateway |
US8605869B1 (en) | 2008-08-08 | 2013-12-10 | Mobilesphere, Ltd. | Method and apparatus for forcing a call to a carrier provided voice mail facility |
US8228861B1 (en) | 2008-09-12 | 2012-07-24 | Nix John A | Efficient handover of media communications in heterogeneous IP networks using handover procedure rules and media handover relays |
US7958233B2 (en) | 2008-09-26 | 2011-06-07 | Media Patents, S.L. | Method for lawfully intercepting communication IP packets exchanged between terminals |
US8275404B2 (en) | 2008-10-29 | 2012-09-25 | Google Inc. | Managing and monitoring emergency services sector resources |
WO2010096127A1 (en) | 2008-10-29 | 2010-08-26 | Terahop Networks, Inc. | Network and application merging and asset tracking |
KR100964375B1 (en) | 2008-10-31 | 2010-06-17 | 한국전자통신연구원 | Interception Method |
US8526306B2 (en) | 2008-12-05 | 2013-09-03 | Cloudshield Technologies, Inc. | Identification of patterns in stateful transactions |
JP5237083B2 (en) | 2008-12-25 | 2013-07-17 | 株式会社エヌ・ティ・ティ・ドコモ | Call control system, call control device, terminal device, and call control method |
WO2010081490A1 (en) | 2009-01-16 | 2010-07-22 | Telefonaktiebolaget L M Ericsson (Publ) | Signalling messages in a communications network node to communicate a called address string |
US8848887B2 (en) | 2009-02-27 | 2014-09-30 | Verizon Patent And Licensing Inc. | Jurisdictionally optimized call routing |
EP2227048A1 (en) | 2009-03-05 | 2010-09-08 | France Telecom | Method for managing user profiles in a peer-to-peer network |
US8396445B2 (en) | 2009-03-12 | 2013-03-12 | At&T Intellectual Property I, L.P. | Method to implement E911 services in IMS (IP Multimedia Subsystem) |
US8989175B2 (en) | 2009-03-18 | 2015-03-24 | Telefonaktiebolaget L M Ericsson (Publ) | Access node comprising VoIP cards with common IP/MAC addresses |
US8315521B2 (en) | 2009-05-01 | 2012-11-20 | Verizon Patent And Licensing Inc. | Peer-to-peer voice over internet protocol |
CN101582798B (en) | 2009-06-19 | 2012-01-11 | 中兴通讯股份有限公司 | Method for remote network management on voice home gateway terminal and system |
WO2011000405A1 (en) | 2009-06-29 | 2011-01-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for relaying packets |
CN101605342B (en) | 2009-07-01 | 2012-12-19 | 中兴通讯股份有限公司 | Method, system and device for monitoring communication contents in IMS network |
US8255393B1 (en) | 2009-08-07 | 2012-08-28 | Google Inc. | User location reputation system |
BR112012003294B1 (en) | 2009-08-14 | 2021-06-22 | Telefonaktiebolaget Lm Ericsson (Publ) | METHOD FOR ESTABLISHING A CONNECTION BETWEEN A SOURCE TERMINAL AND A DESTINATION TERMINAL, NETWORK NODE TO A CORE NETWORK, ACCESS CONNECTION POINT OF A CORE NETWORK, HOLDER OF ELECTRONICALLY LEGIBLE DATA, AND, COMPUTING STORAGE MEANS |
PL2478678T3 (en) | 2009-09-17 | 2016-05-31 | Digifonica Int Ltd | Uninterrupted transmission of internet protocol transmissions during endpoint changes |
US8862701B2 (en) | 2009-09-22 | 2014-10-14 | George Havriluk | Communication network utilizing email or web addresses that describe a physical location |
US8837360B1 (en) | 2009-12-11 | 2014-09-16 | Google Inc. | Determining geographic location of network hosts |
US20110153809A1 (en) | 2009-12-23 | 2011-06-23 | Microsoft Corporation | Legal Intercept |
US8810392B1 (en) | 2010-02-04 | 2014-08-19 | Google Inc. | Device and method for monitoring the presence of items and issuing an alert if an item is not detected |
JP5447042B2 (en) | 2010-03-17 | 2014-03-19 | 株式会社リコー | Control device, control method, and program |
US8819566B2 (en) | 2010-05-04 | 2014-08-26 | Qwest Communications International Inc. | Integrated multi-modal chat |
US9559869B2 (en) | 2010-05-04 | 2017-01-31 | Qwest Communications International Inc. | Video call handling |
US9003306B2 (en) | 2010-05-04 | 2015-04-07 | Qwest Communications International Inc. | Doodle-in-chat-context |
US8468196B1 (en) | 2010-05-20 | 2013-06-18 | Google Inc. | System and method of reducing latency using adaptive retransmission timeouts |
US8228837B2 (en) | 2010-06-17 | 2012-07-24 | Google Inc. | Maintaining network connectivity |
US20120084288A1 (en) | 2010-10-01 | 2012-04-05 | Mohammed Abdul-Razzak | Criminal relationship analysis and visualization |
US8635271B1 (en) | 2010-10-01 | 2014-01-21 | Google Inc. | Method and system for maintaining client cache coherency in a distributed network system |
CN102457494B (en) | 2010-10-20 | 2014-10-01 | 中国移动通信集团四川有限公司 | Method and device for improving monitoring success rate based on session initiation protocol (SIP) signaling |
US8364172B2 (en) | 2010-12-15 | 2013-01-29 | Google Inc. | Peer-to-peer location service |
US20120155333A1 (en) | 2010-12-17 | 2012-06-21 | Electronics And Telecommunications Research Institute Of Daejeon | Appratus and method for lawful interception |
US8938534B2 (en) | 2010-12-30 | 2015-01-20 | Ss8 Networks, Inc. | Automatic provisioning of new users of interest for capture on a communication network |
US20120195236A1 (en) | 2011-02-02 | 2012-08-02 | Comvoice Holdings Llc | System for Multilocation Calling Line Identification Provisioning |
US8972612B2 (en) | 2011-04-05 | 2015-03-03 | SSB Networks, Inc. | Collecting asymmetric data and proxy data on a communication network |
CN102137024B (en) | 2011-04-19 | 2013-11-20 | 福建星网锐捷网络有限公司 | Message processing method, exit routing device and border routing device |
US20140214687A1 (en) | 2011-07-20 | 2014-07-31 | Horatio Nelson Huxham | Cryptographic expansion device and related protocols |
US8948061B2 (en) | 2011-08-09 | 2015-02-03 | Google Technology Holdings LLC | Method of intercepting VOIP communications |
US8924347B1 (en) | 2011-10-05 | 2014-12-30 | Google Inc. | Database replication |
US8599837B2 (en) | 2011-11-18 | 2013-12-03 | Verizon Patent And Licensing Inc. | Local identity based on called number |
US8749610B1 (en) | 2011-11-29 | 2014-06-10 | Google Inc. | Managing nodes of a synchronous communication conference |
US8792374B1 (en) | 2011-12-07 | 2014-07-29 | Google Inc. | Managing network routes from a central server |
CN102572123B (en) | 2011-12-21 | 2014-10-22 | 成都三零瑞通移动通信有限公司 | Method for monitoring call record uploading of eavesdropping software X undercover |
US9305273B2 (en) | 2011-12-31 | 2016-04-05 | Verizon Patent And Licensing Inc. | Telephone number use analysis for grouping of consecutive telephone numbers based on assignment status |
US8712425B2 (en) | 2012-01-11 | 2014-04-29 | Apple Inc. | Managing a packet service call within mobile communications user equipment |
US8391136B1 (en) | 2012-01-27 | 2013-03-05 | Google Inc. | Fallback messaging |
US10484335B2 (en) | 2012-02-09 | 2019-11-19 | Connectify, Inc. | Secure remote computer network |
US9143429B2 (en) | 2012-02-28 | 2015-09-22 | Google Inc. | Identifying an egress point to a network location |
US8792905B1 (en) | 2012-03-01 | 2014-07-29 | Google Inc. | Location monitoring using clusters of entities |
US20130237198A1 (en) | 2012-03-06 | 2013-09-12 | Apple Inc. | System and method for managing data calls |
US9264390B2 (en) | 2012-03-22 | 2016-02-16 | Google Inc. | Synchronous communication system and method |
US8774721B2 (en) | 2012-04-10 | 2014-07-08 | Google Inc. | Detecting a communication tap via signal monitoring |
US8903360B2 (en) | 2012-05-17 | 2014-12-02 | International Business Machines Corporation | Mobile device validation |
WO2014066155A2 (en) | 2012-10-22 | 2014-05-01 | Google Inc. | Monitoring media consumption habits |
CN103973565B (en) | 2013-02-01 | 2017-11-28 | 华为技术有限公司 | It route area selecting method, device and system |
US20140244393A1 (en) | 2013-02-28 | 2014-08-28 | Google Inc. | Fall-back to saved location where user location is unknown |
US9055488B2 (en) | 2013-03-01 | 2015-06-09 | Apple Inc. | Assisting return to a first network from a second network after performance of a circuit switched fallback procedure |
US9338718B2 (en) | 2013-03-14 | 2016-05-10 | Apple Inc. | Voice call resumption on a legacy network |
CN104104781B (en) | 2013-04-09 | 2018-11-23 | 中兴通讯股份有限公司 | A kind of method and device showing SIM cards of mobile phones contact person |
US8903051B2 (en) | 2013-04-12 | 2014-12-02 | Verizon Patent And Licensing Inc. | Returning calls to emergency callers without valid telephone numbers |
US20140337961A1 (en) | 2013-05-08 | 2014-11-13 | Promise Technology, Inc. | System for implementing dynamic access to private cloud environment via public network |
US9282579B2 (en) | 2013-05-23 | 2016-03-08 | Broadcom Corporation | Deactivating elevated priority public data network connections in user equipment |
-
2009
- 2009-07-28 US US13/056,277 patent/US8630234B2/en active Active
- 2009-07-28 EP EP09802316.1A patent/EP2311292B1/en active Active
- 2009-07-28 CA CA2732148A patent/CA2732148C/en active Active
- 2009-07-28 WO PCT/CA2009/001062 patent/WO2010012090A2/en active Application Filing
-
2013
- 2013-09-24 US US14/035,806 patent/US10880721B2/en active Active
-
2020
- 2020-12-28 US US17/135,796 patent/US20210329442A1/en active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070165597A1 (en) * | 2004-06-29 | 2007-07-19 | Damaka, Inc. | System and method for deterministic routing in a peer-to-peer hybrid communications network |
US20060034211A1 (en) * | 2004-08-10 | 2006-02-16 | Fujitsu Limited | Communication apparatus, communication control unit, communication method and computer-readable storage medium |
Also Published As
Publication number | Publication date |
---|---|
CA2732148A1 (en) | 2010-02-04 |
EP2311292A4 (en) | 2014-05-14 |
US20110122827A1 (en) | 2011-05-26 |
WO2010012090A2 (en) | 2010-02-04 |
EP2311292A2 (en) | 2011-04-20 |
EP2311292B1 (en) | 2020-12-16 |
US20140024367A1 (en) | 2014-01-23 |
US8630234B2 (en) | 2014-01-14 |
WO2010012090A3 (en) | 2010-05-06 |
CA2732148C (en) | 2018-06-05 |
US10880721B2 (en) | 2020-12-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210329442A1 (en) | Mobile Gateway | |
US20220070088A1 (en) | Determining a Time to Permit a Communications Session to Be Conducted | |
US11172064B2 (en) | Emergency assistance calling for voice over IP communications systems | |
US10038779B2 (en) | Intercepting voice over IP communications and other data communications |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: VOIP-PAL.COM, INC., CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DIGIFONICA (INTERNATIONAL) LIMITED;REEL/FRAME:054759/0192 Effective date: 20160101 Owner name: DIGIFONICA (INTERNATIONAL) LIMITED, CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BJOERSELL, JOHAN EMIL VIKTOR;SOBOLYEV, MAKSYM;HUTTUNEN, PENTTI KALEVI;AND OTHERS;SIGNING DATES FROM 20110322 TO 20130802;REEL/FRAME:054759/0075 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: ADVISORY ACTION MAILED |
|
STCV | Information on status: appeal procedure |
Free format text: NOTICE OF APPEAL FILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |