Method of setting up a conference call

[0002] The present invention relates generally to the field of telecommunications and more particularly to a method of setting up a conference call.

[0003] Conference calls have proved a cost effective way to hold meetings with people who are located in different parts of the country. The audio quality of a conference call is maintained by connecting all the parties together through a conference bridge. The conference bridge often belongs to a different service provider than the originating service providers for all the parties to the conference call. In addition, the telephone number assigned to the conference bridge is not fixed and may not follow the standard North American Numbering Plan. As a result, when a customer dials the assigned conference number the local exchange carrier has to reoriginate the conference call as an “800” number to the service provider having the conference bridge. This increases the costs of the conference call without providing any benefit to the customer.

[0004] Another problem occurs when a customer has a private branch exchange (PBX) with several service providers including the service provider having the conference bridge. If the customer desires to place an on-network conference call through the service provider with the conference bridge, they cannot ensure that the PBX will select the on-network service provider. When the PBX does not select the on-network service provider the conference call cannot be placed and the call will fail.

[0005] Thus there exists a need for a method of setting up a conference call that reduces the cost of a conference call and will work for a PBX customer wanting to place an on-network conference call.

[0006] A method of setting up a conference call that overcomes these and other problems has the following steps: (1) selecting a conference bridge and a conference number; (2) dialing a conference number; (3) when a private branch exchange seizes an off-network trunk, receiving the conference number at a interexchange carrier service switching point; (4) routing the conference call to a local exchange carrier service switching point; (5) routing the conference call over a dedicated access line to an on-network service switching point; (6) triggering on the conference call at the on-network service switching point; (7) sending a query to a service control point; (8) receiving a routing instructions from the service control point; and (9) routing the conference call to the conference bridge.

[0007] Using the method described above it is no longer necessary for the local exchange carrier to reoriginate the conference call as an “800” number to the service provider of the conference bridge. This reduces the cost of completing a conference call. This method also allows a customer having a PBX connected to several service providers, to place on-network conference calls. This is because the method does not require that the PBX select the on-network service provider in order to complete the call to the service provider's conference bridge. This simplifies the process of placing a conference call for PBX customers.

[0008] FIG. 1 is a block diagram of a telephony system for setting up a conference call;

[0009] FIG. 2 is another embodiment of a block diagram of a telephony system for setting up a conference call;

[0010] FIG. 3 is another embodiment of a block diagram of a telephony system for setting up a conference call;

[0011] FIG. 4 is a flow chart of an embodiment of the steps of setting up a conference call; and

[0012] FIG. 5 is a flow chart of another embodiment of the steps of setting up a conference call.

[0013] FIG. 1 shows a block diagram of a telephony system for setting up a conference call. A customer location has a plurality of telephones 10 connected to a private branch exchange (PBX) 12. The private branch exchange 12 is coupled to an on-network trunk 14 and an off-network trunk 16 (at least two interexchange carriers (IXC) 14, 16). The on-network trunk 14 is connected to an on-network service switching point (SSP) 18. The service switching point 18 is an intelligent switch that routes calls. The service switching point 18 is connected to a service control point (SCP) 20 through a control channel 22. The service control point 20 provides additional information to the service switching point 18, such as designating this call as a conference call, routing instructions to the appropriate conference bridge and billing information. The service switching point 18 is part of a virtual private network (on-network) 24 that connects the conference call to one of a plurality of conference bridges 26 located throughout the virtual private network 24.

[0014] The private branch exchange 12 is also connected to the off-network trunk 16. The off-network trunk 16 connects to the public switched telephone network (PSTN) 28. The interexchange carrier (part of the PSTN) connected to the off-network trunk 16 is connected to the service switching point (conference switch, virtual private network switch) 18 via a dedicated access line 30. It should be understood that the virtual private network 24 encompasses the SSP 18, the control channel 22, the SCP 20 and the conference bridge 26. These elements are broken out separately for clarity and the cloud 24 designates that the conference call can pass through several switches before arriving at conference bridge 26.

[0015] When the customer desires to schedule a conference call he places a phone call to a reservation system. The reservation system assigns an on-network conference call number, alternative off-network conference call number, a conference bridge for the assigned time and a conference call ID. This information is then passed along to a service control point. The customer dials the conference number (on-network telephone number) at the preassigned time from the telephone 10. The PBX 12 seizes either the on-network trunk 14 or the off-network trunk 16. When the PBX 12 seizes the on-network trunk 14 the service switching point 18 is connected to the PBX 12 by a dedicated access line 14. The service switching point 18 triggers on the incoming call because it is on a dedicated access line. The service switching point 18 sends a query over the control channel 22 to the service control point 20. The query includes the following information: the originating switch, originating trunk, and dialed digits. The service control point 20 returns routing instructions based on the conference number. The routing instructions include the terminating switch, the conference ID and a conference call code. The virtual private network 24 then routes the call to the conference bridge 26. The conference bridge 26 then connects all the conferees together.

[0016] When the PBX 12 seizes an off-network trunk 16, the call is routed by the interexchange carrier over the PSTN 28 to the service switching point 18. The call is routed over the PSTN 28 using the standard North American Numbering Plan (or other country's standard routing scheme) routing scheme (standard routing procedure). Note that the call may be routed by at least the originating interexchange carrier and another local exchange carrier before reaching the service switching point 18. The service switching point 18 triggers on the incoming call because it arrives via the dedicated access line 30. In another embodiment the service switching point triggers because the incoming call has a destination number that belongs to a predetermined group of numbers. The service switching point 18 then sends a query to the service control point 20 and receives routing instructions. Based on these routing instructions, the call is routed to the virtual private network 24 and then on to the conference bridge 26.

[0017] FIG. 2 is a block diagram of another embodiment of a telephony system for setting up a conference call. In this embodiment a first user's telephone 50 is connected to a PBX 52. The PBX 52 is connected to an on-network trunk (dedicated access line) 54 and to an off-network trunk 55. The on-network trunk 54 is connected to a first service switching point (SSP) 56. The SSP 56 is connected to a service control point 58 by a control network 60. The SSP 56 is connected to a virtual private network 62 over a voice/data channel 64. The virtual private network is connected to a second SSP 66 that is connected to a designated conference bridge 68.

[0018] The off-network trunk 55 is connected to an off-network interexchange carrier (IXC) 70. The IXC 70 is connected to a first local exchange carrier 72. The local exchange carrier 72 is connected to a second local exchange carrier's service switching point 74. The second local exchange carrier's SSP 74 is connected to a virtual private network SSP 76 over a dedicated access line 78 in one embodiment. The virtual private network SSP 76 is connected to the service control point 58 by a control channel 80. The virtual private network SSP 76 connects to the virtual private network 62. The virtual private network 62 is connected to the second SSP 66, which is connected to the conferencing bridge 68. Note that the virtual private network 62 includes the SSP 56, voice line 64, control network 60, SCP 58, SSP 76, control network 80, SSP 66 and conference bridge 68.

[0019] A second customer telephone 82 is directly connected to a second local exchange carrier 84. The second local exchange carrier 84 is connected via the PSTN to the first local exchange carrier 72.

[0020] Using FIG. 2 several embodiments of the invention will be described. In the first embodiment, the PBX 52 is only connected to the on-network trunk 54. In this case PBX 52 connects conference caller with the first SSP 56 over a dedicated access line 54. The first SSP 56 is part of the on-network or virtual private network. Thus the first SSP 56 triggers either because the call is received over a dedicated access line 54 or because the dialed digits belong to a predetermined set of numbers. The SSP 56 queries the SCP 58 for routing instructions. The SCP 58 sends back routing instructions and information about the conference call. The virtual private network (VPN) 62 then routes the call through SSP 66 to the conference bridge 68.

[0021] In another embodiment the PBX 52 is connected to at least two interexchange carriers 54, 55. When the PBX 52 seizes the on-network trunk 54 the call proceeds as described above. When the PBX seizes the off-network trunk 55, the off-network IXC (interexchange carrier service switching point) 70 routes the call based on standard North American Plan Numbering routing. The call is received by the LEC 72 that continues to route the call using standard processing to the second LEC SSP 74. The second LEC SSP 74 determines that the dialed number belongs to a predetermined set of telephone numbers and routes the call over the dedicated access line 78 to the virtual private network SSP 76. The SSP 76 triggers on the incoming call because the call is received over the dedicated access line 78. The SSP 76 sends a query to the SCP 58 and receives routing instructions to the conference bridge 68. The call is then routed through the VPN 62 and SSP 66 to the conference bridge 68.

[0022] In another embodiment the PBX 52 is programmed to determine if dialed number belongs to a predetermined set of numbers, such as a pseudo-telephone number (non-North American Dialing Plan number), on-network numbers or an unused group of standard numbers. When the dialed number belongs to the predetermined set of numbers the call is routed over the dedicated access line (on-network trunk) 54 to the on-network SSP 56. Processing then proceeds as described above for the on-network case.

[0023] In another embodiment the conference call number is a pseudo number. When the PBX 52 seizes the on-network trunk 54 processing proceeds as a standard on-network call. When the PBX 52 seizes the off-network trunk 55, the off-network IXC 70 is unable to place the call. The off-network IXC 70 then returns a message that the call cannot be completed.

[0024] In another embodiment the conferee places the call from telephone directly connected to the LEC 84. In this case the conference telephone number can be either an “800” number or on-network telephone number that conforms to the North American Numbering Plan. Assuming the conference number conforms to the North American Numbering Plan the LEC 84 routes the call using standard routing through the PSTN to another LEC 72. The LEC 72 routes the call to a second LEC SSP (local switch) 74. A group of numbers are reserved at this SSP 74 for conference calls. When a call to one of the group of reserved numbers is received at the SSP 74, it is routed over the dedicated access line 78 to virtual private network SSP 76. The SSP 76 triggers on the incoming call because it is received over the dedicated access line 78. The SSP 76 then sends a query to the SCP 58 and receives routing instructions. Based on these routing instructions, the call is routed through the VPN 62, the SSP 66 to the conferencing bridge 68.

[0025] FIG. 3 is a block diagram of another embodiment of a telephony system for setting up a conference call. In this embodiment a customer uses a desktop system 100 at a customer location (subscriber location). In one embodiment, the desktop system 100 is a computer with a speaker 102, a microphone 104, a display 106 and optionally a camera 108. The desktop system 100 is connected through a local area network 110 to a router (customer switch) 112. The router 112 is connected to a virtual private network 114 and a public network 116. The virtual private network 114 is connected to a conference bridge 118. The public network is connected to a conference switch (router) 120. The router 120 is connected to the virtual private network 114.

[0026] The user places a conference call by entering a conference address on the desktop system 100. The customer switch (router) 112 can seize either a connection to the virtual private network 114 or to the public network 116. When the connection to the public network 116 is seized, the call is routed using standard routing (e.g., TCP/IP routing) to the conference switch 120. The conference switch 120 then determines that the conference address requires routing to the virtual private network 114. The virtual private network 114 then routes the call to the designated conference bridge 118. When the router 112 seizes the connection to the virtual private network 114, the virtual private network routes the call to the conference bridge 118 based on instructions programmed into the switches of the VPN 114.

[0027] In another embodiment, the router 112 determines if the conference address belongs to a predetermined set of address. When the conference address belongs to the predetermined set of address, the call is routed over the connection to the virtual private network.

[0028] FIG. 4 is a flow chart of an embodiment of the steps of setting up a conference call. The process starts, step 150, by the customer dialing an on-network telephone number at step 152. At a switch it is determined if the on-network number belongs to predetermined set of numbers at step 154. Note that the switch can be a PBX, a SSP or a router. When the on-network number does not belong to the predetermined set of numbers the call is sent to the public network for processing at step 156. When the on-network number does belong to the predetermined set of numbers (group of on-network numbers), the call is routed to a virtual private network at step 158. The virtual private network then routes the call to the designated conference bridge at step 160, which ends the process at step 162.

[0029] FIG. 5 is a flow chart of another embodiment of the steps of setting up a conference call. The process starts, step 180, by selecting a conference bridge and a conference telephone number at step 182. The user then dials the conference telephone number at step 184. Next it is determined if the PBX selects an off-network trunk at step 186. When the PBX selects the off-network trunk, the call is routed through an interexchange carrier (IXC) to a Service Switching Point (SSP) at step 188. The SSP routes the call over a dedicated access line to an on-network SSP at step 190. Note that when the PBX does not select the off-network trunk at step 186, processing proceeds to step 190. Next, a query is sent to a Service Control Point (SCP) at step 192. At step 194, routing instructions are received from the SCP. Using the routing instructions the call is routed to the designated conference bridge at step 196, which ends the process at step 198.

[0030] Thus there has been described a method of setting up a conference call that reduces the cost of a conference call and will work for a PBX customer wanting to place an on-network conference call. While the invention has been described in conjunction with specific embodiments thereof, it is evident that many alterations, modifications, and variations will be apparent to those skilled in the art in light of the foregoing description. Accordingly, it is intended to embrace all such alterations, modifications, and variations in the appended claims.