Network system for routing calls

BACKGROUND OF THE INVENTION

The invention relates to a network system provided with call forwarding means.

There are currently two types of routing mechanisms, namely 5 routing from terminal to terminal (TTR: Terminal to Terminal

Routing) and subscriber to terminal routing (UTR: User to Terminal Routing). TTR includes services such as secretary function, follow-me, etc .; UTR includes UPT-related services (UPT: Universal Personal Telecommunications).

So far, different servers are used for TTR and UTR, the heart of which is formed by a database in which the called terminal resp user is linked to a (different) terminal. Using different servers or platforms can lead to system conflicts if the same user wants to use both services simultaneously. System conflicts can only be avoided by making the control of the TTR or UTR system more complex.

SUMMARY OF THE INVENTION

The object of the invention is to provide a solution to the problem posed by transforming, as it were, TTR actions into UTR actions, whereby use can be made of the same operating system, namely the UTR controller. This does not change for UTR; the term anonymous user is introduced to perform TTR functions. In addition, a terminal is always proposed by an (anonymous) user or, in other words, terminals to which routing must be made are indicated by an (anonymous) user designation. This designation can also have the format of terminal designations: the anonymous user designation is then equated with the terminal designation.

This will be explained in more detail below on the basis of an exemplary embodiment.

IMPLEMENTATION EXAMPLE

Figure 1 shows an embodiment of the invention. The figure shows a network, controlled by a network server, to which a number of nodes N1 ... N5 and a number of workstations T1 ... T5 are connected. The network server includes a routing table. The routing information can be set and changed by the network users, in the figure the users U1 ... U3. In accordance with the routing table, the network server will route calls for UI to node N3, thereby reaching user UI who has chosen domicile on terminal T3 connected to node N3. In the same way, calls for U2 arrive at the terminal at which U2 has chosen domicile, and calls for U3 at terminal T5 at which it can be reached. The mentioned users U1 ... U3 have previously communicated to the network server where they can be reached, for example by entering their personal user ID via the terminal where they choose domicile. The network server then registers their user ID (U #) and the node ID (N #) through which that registration arrives at the network server, resulting in the first three lines of the routing table in the figure. If user UI prefers to be accessible via terminal T4 at some point, he can pass this on via terminal T3 or terminal T4, as a result of which table UI N3 changes to UI N4. Re-routing of terminals, regardless of who the user is (anonymous user), can also be done in the same way and with the same means,

ic the same routing table. For example, UI can pass that all calls to T3 are to be routed to T2, more accurately, to node N2. UI continues to receive calls addressed to him, UI, at T3.

System conflicts do not arise by using the same database and control for UTR and for TTR, in contrast to the prior art. An anonymous user can bypass one of the terminals T1 ... T5: the table shows that terminal Tl has been routed to node N3, which means that all calls destined for Tl, that is, for any anonymous user in the vicinity of

Tl, end up at T3. T2 and T4 are not routed, while T3 and T5 are routed to T2, via N2, respectively. Tl, via Nl.

<img file="NL1007335C2_D0001.tif" />