 |
|
10.7 |
E.164 Numbering Plan |
| Numbering types: |
| • | Closed numbering Station numbers are unique within an individual location. A node number is not necessary. The stations are addressed via their internal station number. |
| • | Open numbering Station numbers are not unique within an individual location. A node number is necessary. The node number is entered as a prefix in front of an internal station number for outbound dialing. |
| In addition to these types of numbering, HiPath 3000/5000 systems in V7 and later offer E.164 numbering. |
|
| The E.164 Numbering Plan feature is used to network cross-location or globally distributed customer systems. Stations can be reached over a public station number, that is, the E.164 station number in national or international format. Every station is represented by its E.164 station number that can be optimized for display. The advantage of this is that you can reach a station via a station number without having to dial node numbers first. |
| Numbering plan requirements are based on the following: |
| • | Customers with multiple locations generally have an open numbering plan. |
| • | Customers are active at multiple locations within a single country or on a global level. |
| • | Customers do not want to have to dial the node code as well as the station number because this would involve maintaining an additional internal phonebook. |
| • | Options must be provided for dialing public station numbers, for example, from the local internal phonebook or via LDAP. |
| • | In addition to the name, a reasonable portion of the station number should be displayed, that is, it should be as short as possible without national or area code and without the local number. |
| • | A numbering scheme should apply universally and aross all platforms for all types of network. |
| This, however, means that the assignment of certain station number ranges to the relevant locations is no longer necessary in E.164 networking. If a subscriber relocates from one location to another, a technician can set up the subscriber's old station number at the new location, as long as it is still free. |
| Networking in the E.164 numbering plan means that subscribers can call network-internal stations using an E.164 number. If E.164 is not active, then the subscriber must dial the station number or node number plus station number as usual. |
| It is necessary to activate the system-wide E.164 flags so that the internal station number can be sent in E.164 format. Up until now this wasn't possible. |
| Configuring the Type of Number of the Called Party Number is only possible when LCR is activated. |
| The E.164 format is supported in the following information elements: |
| • | Calling Party Number (internal station number) |
| • | Additional Party Number (DUWA number) |
| • | Connected Number |
| • | Called Party Number |
| • | Diverted Number |
| In the case of E.164, these numbers are assigned the numbering plan (NP) = ISDN. The type of number is usually set to international, but can also be configured to national or subscriber. |
| How the station is dialed and how the station number is finally displayed on the line is controlled by LCR. Digit analysis is performed a second time on the HG 1500 (station number analysis of the voice gateway HG 1500) in the case of outbound dialing. |
Behavior for networking with HiPath 5000 RSM |
| A HiPath 5000 RSM network can be integrated into an existing E.164 network (e.g. network with HiPath 4000) with the limitation that subscribers in the HiPath 5000 RSM network can only be called on their internal station number. This is because all subscribers were entered in the CAR tables in the HiPath 5000 RSM network with their internal number from the HiPath 5000 RSM. To reach internal dialing in the RSM network, the Called Party Number must be shortened. To do this, each node must know the ISDN station number of all other nodes. Subscribers outside the HiPath 5000 RSM network can be called with the E.164 station number. |
| A HiPath 5000 RSM network can only have closed numbering. |
| HiPath 3000/5000 V8, Feature Description, Issue 10 | up  |
|
|
||
| Disclaimer & Copyright | ID: P31003H3580F100017618 | 2011-02-07 |