.rs .\" Troff code generated by TPS Convert from ITU Original Files .\" Not Copyright ( c) 1991 .\" .\" Assumes tbl, eqn, MS macros, and lots of luck. .TA 1c 2c 3c 4c 5c 6c 7c 8c .ds CH .ds CF .EQ delim @@ .EN .nr LL 40.5P .nr ll 40.5P .nr HM 3P .nr FM 6P .nr PO 4P .nr PD 9p .po 4P .rs \v | 5i' .sp 1P .ce 1000 \v'3P' SECTION\ 5 .ce 0 .sp 1P .ce 1000 \fBNUMBERING\ PLAN\ OF\ THE\ INTERNATIONAL\ TELEPHONE\ SERVICE\fR .ce 0 .sp 1P .sp 2P .LP \fBRecommendation\ E.160\fR .RT .sp 2P .ce 1000 \fBDEFINITIONS\ RELATING\ TO\ NATIONAL\fR .EF '% Fascicle\ II.2\ \(em\ Rec.\ E.160'' .OF '''Fascicle\ II.2\ \(em\ Rec.\ E.160 %' .ce 0 .sp 1P .ce 1000 \fBAND\ INTERNATIONAL\ NUMBERING\ PLANS\fR .ce 0 .sp 1P .LP \fB1\fR \fBprefix\fR .sp 1P .RT .LP \fIF:\ pr\*'efixe\fR .LP \fIS:\ prefijo\fR .PP A prefix is an indicator consisting of one or more digits, that allows the selection of different types of number formats (e.g.,\ local, national or international), transit networks and/or the service. .PP Prefixes are not part of the number and are not signalled over internetwork or international boundaries. .PP \fINote\fR \ \(em\ When prefixes are used, they are always entered by the user or automatic calling equipment. .RT .sp 2P .LP \fB2\fR \fBinternational prefix\fR .sp 1P .RT .LP \fIF:\ pr\*'efixe international\fR .LP \fIS:\ prefijo internacional\fR .PP The combination of digits to be dialled by a calling subscriber making a call to a subscriber in another country to obtain access to the automatic outgoing international equipment. .PP Example: .PP 00\ \ in Switzerland. .PP \fINote\ 1\fR \ \(em\ In some countries two or more international prefixes may be used: .RT .LP \(em to reach different groups of countries; .LP \(em to obtain different classes of call (e.g., station call or personal call). .PP In the first case the use of two or more international prefixes allows the use of different groups of switching equipment and the use of \fIabbreviated\fR dialling (i.e., shorter country codes) for the calls to a defined group of countries (see the definition, \fIcountry code\fR in \(sc\ 5). .PP \fINote\ 2\fR \ \(em\ Where several countries are included in one integrated numbering plan, the international prefix is not used on a call from one of these countries to another. .bp .RT .sp 2P .LP \fB3\fR \fBnational (trunk) prefix\fR .sp 1P .RT .LP \fIF:\ pr\*'efixe (interurbain) national\fR .LP \fIS:\ prefijo (interurbano) nacional\fR .PP A digit or combination of digits to be dialled by a calling subscriber, making a call to a subscriber in his own country but outside his own numbering area. It provides access to the automatic outgoing trunk equipment. .PP Examples: .RT .LP \ \ \fBand\fR \ \ 0 in Belgium, Italy, Japan, Netherlands, Switzerland, United Kingdom; .LP 1\ and\ \ 0 in Canada and in the USA; .LP \ \ \fBand\fR \ \ 9 in Finland and Spain; .LP \ \ \fBand\fR \ 16 in France. .PP \fINote\fR \ \(em\ In the case where several countries are included in one integrated numbering plan, the national (trunk) prefix is also used for calls from one of these countries to another. .sp 2P .LP \fB4\fR \fBescape code\fR .sp 1P .RT .LP \fIF:\ code d'\*'echappement\fR .LP \fIS:\ c\*'odigo de escape\fR .PP An escape code is an indicator consisting of one or more digits which is defined in a given numbering plan and is used to indicate that the digits that follow are from a specific numbering plan which is different from the given numbering plan. .PP For example, escape codes are currently used within the X.121 numbering plan to interwork with E.164 (ISDN) and F.69 (Telex) numbering plans. .PP An escape code can be carried forward through the originating network and can be carried across internetwork and international boundaries. Therefore the digits used for escape codes should be standardized. .RT .sp 2P .LP \fB5\fR \fBcountry code\fR .sp 1P .RT .LP \fIF:\ indicatif de pays\fR .LP \fIS:\ indicativo de pa\*'is\fR .PP The combination of one, two or three digits characterizing the called country. .PP Examples: .RT .LP \ \ 7\ USSR; .LP \ 54 Argentina; .LP 591 Bolivia. .PP \fINote\ 1\fR \ \(em\ In the case where a country uses different international prefixes, abbreviated dialling can be used. In this case, for calls to one country of a defined group of countries, a regional country code, composed of fewer digits than the normal country code, may be used. .PP Examples: .RT .LP For traffic between Latin American countries, the following regional country codes might be used: .LP 1 Argentina; .LP 2 Brazil; .LP 3 Chile, etc. .PP \fINote\ 2\fR \ \(em\ In the case where several countries are included in one integrated numbering plan, no country code need be dialled for the traffic from one of these countries to another. For access by other countries, these countries: .LP \(em may be included under one common country code, or .LP \(em may have separate country codes, .LP always keeping in mind the necessity to avoid exceeding the recommended maximum number of digits in the international number. .bp .sp 2P .LP \fB6\fR \fBtrunk code\fR .sp 1P .RT .LP \fIF:\ indicatif interurbain\fR .LP \fIS:\ indicativo interurbano\fR .PP A digit or combination of digits [not including the national (trunk) prefix] characterizing the called numbering area within a country (or group of countries included in one integrated numbering plan). .PP The trunk code has to be dialled before the called subscriber's number where the calling and called subscribers are in different numbering areas. .PP The trunk code varies from one country to another and is composed of: .RT .LP a) Either a \fIregional code\fR | indicating the geographical zone to which the called subscriber belongs and within which subscribers can call one another by their subscriber numbers. .LP Examples: .LP \fIIn France:\fR .LP Paris area (Departments of Seine, Yvelines, Seine\(hyet\(hyMarne, Oise, etc.):\ trunk code\ 1, .LP Nice area (Department of Alpes\(hyMaritimes):\ trunk code\ 93; .LP \fIIn Belgium:\fR .LP Bruxelles area:\ trunk code\ 2, .LP Namur area:\ trunk code\ 81; .LP \fIIn the Federal Republic of Germany and the Netherlands:\fR .LP the geographical area defined above corresponds in general to the local network: .LP D\*:usseldorf local network:\ trunk code\ 211, .LP Amsterdam local network:\ trunk code\ 20; .LP \fIIn the United Kingdom:\fR .LP this definition applies to certain networks such as that of London, for which the trunk code is\ 1; .LP \fIIn Canada and the USA:\fR .LP the geographical area defined above corresponds to a \fINumbering Plan Area\fR (NPA): .LP Montr\*'eal area:\ NPA code\ 514, .LP New York City area:\ NPA code\ 212; .LP b) Or a \fInumbering area code\fR | followed by an exchange code when the directory entry of the called subscriber does not include the exchange code; .LP Examples: .LP \fIIn certain areas of the United Kingdom:\fR .LP Truro (group centre):\ trunk code\ 872, .LP Perranporth (in the Truro group):\ trunk code\ 872 57. .sp 2P .LP \fB7\fR \fBsubscriber number\fR .FS Care should be taken not to use the term \*Qlocal number\*U instead of \*Qsubscriber number\*U. .FE .sp 1P .RT .LP \fIF:\ num\*'ero d'abonn\*'e\fR .LP \fIS:\ n\*'umero de abonado\fR .PP The number to be dialled or called to reach a subscriber in the same local network or numbering area. .PP This number is the one usually listed in the directory against the name of the subscriber. .bp .RT .sp 2P .LP \fB8\fR \fBnational (significant) number\fR .sp 1P .RT .LP \fIF:\ num\*'ero national (significatif)\fR .LP \fIS:\ n\*'umero nacional (significativo)\fR .PP The number to be dialled following the national (trunk) prefix to obtain a subscriber in the same country (or group of countries included in one integrated numbering plan) but outside the same local network or numbering area. .PP The national (significant) number consists of the trunk code followed by the subscriber number. .PP It should be noted that, in some countries, it is customary to consider \fIfor national purposes\fR | that the national (trunk) prefix is included in the national number [which is then not the national (significant) number]. A careful distinction must therefore be made between such national definition or practice and the CCITT definition, which is internationally valid. In order to avoid misunderstanding, the CCITT definition includes the word \*Qsignificant\*U between brackets, reading as follows:\ \*Qnational (significant) number\*U. .PP Examples: .RT .LP \ \ \ \ \fISubscriber\fR \fINational (significant) number\fR .LP 123 | 5 | 7\ in\ Bruxelles \ \ 2 | 23 | 5 | 7 .LP \ 12 | 4 | 6\ in\ D\*:usseldorf 211 | 12 | 4 | 6 .LP 870 | 2 | 4\ in\ Montr\*'eal 514 | 70 | 2 | 4 .LP \ \ \ | 2 | 4\ in\ Perranporth 872 | 57 | 2 | 4 .LP 248 | 5 | 7\ in\ London \ \ 1 | 48 | 5 | 7 .PP \fINote\fR \ \(em\ Where several countries are included in one integrated numbering plan, only the national (significant) number is to be dialled after the national (trunk) prefix on calls from one of these countries to another. .sp 2P .LP \fB9\fR \fBinternational number\fR .sp 1P .RT .LP \fIF:\ num\*'ero international\fR .LP \fIS:\ n\*'umero internacional\fR .PP The number to be dialled following the international prefix to obtain a subscriber in another country. .PP The international number consists of the country code of the required country followed by the national (significant) number of the called subscriber. .PP Examples: .RT .LP \ \ \ \ \fISubscriber\fR \fIInternational number\fR .LP 123 | 5 | 7\ in\ Bruxelles 32 | \ 2 | 23 | 5 | 7 .LP \ 12 | 4 | 6\ in\ D\*:usseldorf 49 | 11 | 12 | 4 | 6 .LP 870 | 2 | 4\ in\ Montr\*'eal \ 1 | 14 | 70 | 2 | 4 .LP \ \ \ | 2 | 4\ in\ Perranporth 44 | 72 | 57 | 2 | 4 .LP 248 | 5 | 7\ in\ London 44 | \ 1 | 48 | 5 | 7 .PP \fINote\fR \ \(em\ Where several countries are included in one integrated numbering plan, the international number is not used on calls from one of these countries to another. (See the note to Definition\ No.\ 8.) .sp 2P .LP \fB10\fR \fBnational destination code (NDC)\fR .sp 1P .RT .LP \fIF:\ indicatif national de destination (IND)\fR .LP \fIS:\ indicativo nacional de destino (IND)\fR .PP A code field, within the E.164 numbering plan, which combined with the subscriber's number (SN) will constitute the national (significant) number of the international ISDN number. The NDC will have a network and/or trunk code selection function. .PP The NDC can be a decimal digit or a combination of decimal digits (not including any prefix) characterizing a numbering area within a country (or group of countries included in one integrated numbering plan). .PP The NDC has to be inserted before the called subscriber's number when the calling and called parties are located in different number areas. .bp .PP NDC assignments are a national responsibility and therefore the NDC structure varies from one country to another. It may take a trunk code format or serve for selection of a destination network. .PP The NDC can in some instances, provide a combination of both the above functions. .RT .sp 2P .LP \fB11\fR \fBdestination network (DN) code\fR .sp 1P .RT .LP \fIF:\ indicatif de r\*'eseau de destination (RD)\fR .LP \fIS:\ indicativo de red de destino (RD)\fR .PP An optional code field within the E.164 numbering plan which identifies the destination network serving the destination subscriber. It performs the destination network selection function of the NDC. In some instances it can be combined with a trunk code to form the NDC. The DN\ code can be a decimal digit or a combination of decimal digits (not including any prefix). .RT .sp 2P .LP \fBRecommendation\ E.161\fR .RT .sp 2P .ce 1000 \fBARRANGEMENT\ OF\ FIGURES,\ LETTERS\ AND\ SYMBOLS\fR .EF '% Fascicle\ II.2\ \(em\ Rec.\ E.161'' .OF '''Fascicle\ II.2\ \(em\ Rec.\ E.161 %' .ce 0 .ce 1000 \fBON\ TELEPHONES\ AND\ OTHER\ DEVICES\ THAT\ CAN\ BE\ USED\fR .ce 0 .sp 1P .ce 1000 \fBFOR\ GAINING\ ACCESS\ TO\ A\ TELEPHONE\ NETWORK\fR .ce 0 .sp 1P .LP \fB1\fR \fBUse of figures and letters in telephone numbers\fR .sp 1P .RT .PP 1.1 For the automatic international service, it is preferable that the national numbering plan should not involve the use of letters (associated with figures). The use of letters in national number plans may, however, be necessary for national reasons. For example, countries using letters in their subscriber numbers will naturally use them in their national numbering. .sp 1P .RT .PP 1.2 For the automatic international service to countries using letters in telephone numbers, it would be helpful, in a country where letters are not used: .LP a) to include in the directory a table for converting into figures the letter codes of exhanges in countries with which an automatic service is available; .LP b) to supply, at the time of opening this automatic service, a booklet of instructions containing the conversion table to the main subscribers to the international service. .PP 1.3 It would also be desirable, in countries with letters in the telephone numbers, that subscribers with considerable international traffic should be asked to show on their letterheads, below their national telephone number, the international number with figures only. (See Recommendation\ E.123.) .sp 2P .LP \fB2\fR \fBRotary dials\fR (see Figure 1/E.161) .sp 1P .RT .PP 2.1 For countries which have not yet adopted any specific type of dial, the figures on the dial should be arranged in the following order: 1,\ 2,\ 3, . | | , 0. .sp 9p .RT .PP 2.2 The dial shown in Figure 1/E.161 uses the arrangement of letters and figures employed by some European Administrations. It may be convenient that the dials or pushbotton sets used by international operators for semiautomatic operating in Europe have this arrangement of letters and figures. .PP \fINote\fR \ \(hy\ On the North American dials and keysets, the digit 0 is not associated with letters O and Q but with the word \fIoperator\fR , the letter O being associated with digit\ 6. .bp .LP .rs .sp 16P .ad r \fBFigure 1/E.161, p.\fR .sp 1P .RT .ad b .RT .LP \fB3\fR \fBPushbuttons or keys\fR .sp 1P .RT .sp 2P .LP 3.1 \fI10 pushbuttons\fR .sp 1P .RT .sp 1P .LP 3.1.1 \fIArrangement and numbering\fR .sp 9p .RT .PP The standard arrangement and numbering for pushbuttons corresponding to the digits 1 to 0 is as shown below: .RT .sp 1P .ce 1000 \fB1\ 2\ 3\fR .ce 0 .sp 1P .ce 1000 \fB4\ 5\ 6\fR .ce 0 .sp 1P .ce 1000 \fB7\ 8\ 9\fR .ce 0 .sp 1P .ce 1000 \fB\ \ 0\ \ \fR .ce 0 .sp 1P .PP Extensive research has shown that this arrangement leads to shorter entry times and lower error rates than other arrangements .FS An annotated list of literature references is available in the article cited in [1]. .FE . .PP Where a need exists within an Administration for a 2 \(mu 5 array or a 5\ \(mu\ 2 array for use on special telephone apparatus, the arrays should be as shown below: .RT .LP \fB1\ 2\fR .LP \fB1\ 2\ 3\ 4\ 5\fR \fB3\ 4\fR .LP \fB6\ 7\ 8\ 9\ 0\fR \fB5\ 6\fR .LP \fB7\ 8\fR .LP \fB9\ 0\fR .PP \fINote\fR \ \(em\ User dialling performance on these special arrays is slightly inferior to that on the standard array given above. .bp .PP In view of the fact that purely numerical numbering plans are now recommended and that the association of letters to digits is not the same in different countries .FS Thus, for example, on the North American dials and keysets, the digit 0 is not associated with letter O and Q but with the word \fIoperator\fR , the letter O being associated with the digit 6. .FE , it is not desirable to standardize letter symbols for the pushbuttons corresponding to each of the digits. In cases where a mixed letter\(hyand\(hydigit dialling system is still in use in a country, the letters associated with the figures in the dialling system of the country concerned may, of course, be included on the corresponding pushbuttons of this country's telephone sets (see Figure\ 2/E.161). .RT .LP .rs .sp 14P .ad r \fBFigure 2/E.161, p.\fR .sp 1P .RT .ad b .RT .PP The preferred and recommended arrangement for the keys of a separate numeric keypad on a multi\(hyfunctional terminal used both for the entry of telephone number information and data is the standard arrangement shown at the beginning of this section. .PP Exceptionally, for devices intended to be used principally for data entry but which may sometimes be used to enter telephone number information, the arrangment whereby the first and the third row of the standard CCITT arrangement are interchanged may be used .FS The corresponding ISO standard can be found in ISO Draft Proposal 9995, entitled: \*QKeyboard Layouts for Text and Office Systems\*U. .FE . .PP Also exceptionally, telephone number information may be input from the row of numeric keys, .RT .sp 1P .ce 1000 \fB1\ 2\ 3\ 4\ 5\ 6\ 7\ 8\ 9\ 0\fR .ce 0 .sp 1P .LP of an alpha\(hynumeric keyboard. .sp 1P .LP 3.1.2 \fISymbols\fR .sp 9p .RT .PP The symbols for these buttons are the digits 1 to 0 as indicated in the arrangements of \(sc\ 3.1.1 above. These buttons are to be known as button\ 1, button\ 2, etc. .RT .sp 2P .LP 3.2 \fI12 pushbuttons\fR .sp 1P .RT .sp 1P .LP 3.2.1 \fIArrangement\fR .sp 9p .RT .PP For 12 pushbuttons the standard arrangement shown in \(sc\ 3.1.1 above is extended by two additional buttons, one to the left and the other to the right of the button\ 0, thus making a pattern of four horizontal rows of three buttons each forming a 4\ \(mu\ 3 array. .PP Two buttons may also be added to the 5\ \(mu\ 2 array shown in \(sc\ 3.1.1 above. These should be located below and in line with buttons\ 9 and\ 0, thus making a 6\ \(mu\ 2 array. .bp .RT .sp 1P .LP 3.2.2 \fISymbols\fR .sp 9p .RT .PP On the 4 \(mu 3 array, the symbol on the button which is immediately to the left of the button 0 (on the 6\ \(mu\ 2 array, the corresponding button is located below 9, and on the 2\ \(mu\ 6 array to the right of button 5) and which, according to Recommendation\ Q.23, is used to transmit the frequency pair 941\ Hz, should have a shape easily identified as the general shape shown in Figure\ 3/E.161. .RT .LP .rs .sp 6P .ad r \fBFigure 3/E.161, p.\fR .sp 1P .RT .ad b .RT .PP The symbol will be known as the \fIstar\fR | or the equivalent term in other languages. .PP On the 4\ \(mu\ 3 array, the symbol on the button which is immediately to the right of the button\ 0 (in the 6\ \(mu\ 2 array, the corresponding button is located below the button\ 0) and which, according to Recommendation\ Q.23, is used to transmit the frequency pair 941\ Hz and 1477\ Hz, should conform in shape to the specifications given in Figures\ 4/E.161 or 5/E.161. This symbol shall consist of four lines of equal length (b), forming two pairs of parallel lines. One pair is horizontal while the other is vertical or inclined to the right at an angle \(*a of 80 | (de as shown in Figure\ 5/E.161. It will be seen that two pairs of parallel lines overlap. The ratio a/b, where a is the overlap, shall be between\ 0.08 and\ 0.18. .RT .LP .rs .sp 9P .ad r \fBFigure 4\(hy5/E.161, p.\fR .sp 1P .RT .ad b .RT .PP The preferred values are: .LP No information is available at the present time as to which of these values would be preferred in other continents. .FE \(em in Europe .LP \(*a = 90 | (de with \fIa\fR /\fIb\fR = 0.08 .LP \(em in North America .LP \(*a = 80 | (de with \fIa\fR /\fIb\fR | close to the upper limit of 0.18. .PP The symbol will be known as the \fIsquare\fR | or the most commonly used equivalent term in other languages .FS In some countries an alternative term (e.g.,\ \*Qnumber sign\*U) may be necessary for this purpose, unless further investigation indicates that \*Qsquare\*U is suitable for the customer. .FE . .bp .PP The additional buttons with these symbols will be placed as shown below: .RT .LP .sp 1 Standard\ 4\ \(mu\ 3\ array 6\ \(mu\ 2\ array 2\ \(mu\ 6\ array \fB1\ 2\ 3\fR \fB1\ 2\fR \fB1\ 2\ 3\ 4\ 5\ *\fR \fB4\ 5\ 6\fR \fB3\ 4\fR \fB | \ 7\ 8\ 9\ 0\ | #\fR \fB7\ 8\ 9\fR \fR \fB5\ 6\fR \fB | \ 0\ | #\fR \fB7\ 8\fR \fB9\ 0\fR \fB | \ | #\fR .sp 1P .LP 3.3 \fIDual mode and engraving\fR .sp 9p .RT .PP Dual mode and engraving of the buttons * and ## are acceptable on telephones and on multi\(hyfunctional terminals. .RT .sp 1P .LP 3.4 \fIDesign of symbols\fR .sp 9p .RT .PP Symbol size and the line thickness should be appropriate to provide optimal recognition. .RT .sp 1P .LP 3.5 \fIUse of colours\fR .sp 9p .RT .PP The question of standardization of pushbutton and symbol colour for international purposes is still not settled. In the meantime, colours different from the digit buttons and symbols should not be used. .RT .sp 1P .LP 3.6 \fIPosition of figures, letters and symbols on push\(hybutton sets\fR .sp 9p .RT .PP In all push\(hybutton dials, the figures, letters and symbols should be unambiguously associated with the corresponding buttons, preferably, if adequate space is available, by being on the faces of the buttons themselves. .RT .sp 2P .LP \fB4\fR \fBAdditional pushbuttons for use on telephones\fR .sp 1P .RT .sp 1P .LP 4.1 \fIGeneral\fR .sp 9p .RT .PP For purposes other than dialling, additional pushbuttons may be required on a telephone. For example, a telephone may have a pushbutton to recall during an active call, control logic (e.g.,\ a register) or an operator, or to effect the transfer of an active call to another station. To prevent subscriber confusion it may be desirable that the symbols used on those pushbuttons which have identical functions be standardized. .RT .sp 2P .LP 4.2 \fISpecific recommendations\fR .sp 1P .RT .sp 1P .LP 4.2.1 \fIRegister recall pushbutton\fR .sp 9p .RT .PP For the recall of a register during an active call the following methods are possible: .RT .LP \(em a switchhook flash, .LP \(em a depression of one of the pushbuttons of the normal 10 or 12 button array, .LP \(em a depression of another pushbutton specially provided for this purpose \(em the register recall pushbutton. .PP From the human factors viewpoint the depression of a pushbutton for register recall seems to be preferable to the use of a switchhook flash. .bp .PP If a special register recall pushbutton is used, this pushbutton should be designated with the symbol R (capital) on or next to the pushbutton. The pushbutton should be clearly distinguishable and spatially separated from the standard 12\(hypushbutton array. .PP This symbol is recommended because: .RT .LP a) it symbolizes the term \*QRecall\*U in a number of languages; .LP b) studies have shown that it is subject to minimal auditory and visual confusion; .LP c) it avoids the difficulties inherent in specific technical terms for any lay subscribers. .PP The exact position, shape and colour of the button should not be standardized at the present time. Such standardization would inhibit design innovation and be unnecessarily restrictive. .PP \fINote\fR \ \(em\ Description of a 16\(hypushbutton layout has been deleted from this Recommendation owing to lack of use of this arrangement. Reference to 16\ pushbutton sets can be found in the CCITT \fIRed\ Book\fR , Fascicle\ II.2, Recommendation\ E.161, \(sc\ 3.3 and Annex\ A. .RT .sp 2P .LP \fBReference\fR .sp 1P .RT .LP [1] \fIThe layout of digits on push\(hybutton telephones\fR \(em a review of the literature. \fITELE\fR , No. 1, 1982 (copies available at the Library of the Swedish Telecommunication Headquarters, S\(hy12386 FARSTA). .sp 2P .LP \fBRecommendation\ E.163\fR .FS This Recommendation is also included in the Series\ Q Recommendations under the number Q.11. .FE .RT .sp 2P .sp 1P .ce 1000 \fBNUMBERING\ PLAN\ FOR\ THE\ INTERNATIONAL\ TELEPHONE\ SERVICE\fR .EF '% Fascicle\ II.2\ \(em\ Rec.\ E.163'' .OF '''Fascicle\ II.2\ \(em\ Rec.\ E.163 %' .ce 0 .sp 1P .LP \fBIntroduction\fR .sp 1P .RT .PP This Recommendation describes the numbering plan for the International Telephone Service. Recommendation\ E.164 describes the numbering plan for the ISDN era. It is for each Administration to choose the method of application from the two Recommendations which would provide the optimum approach to meeting their future national numbering plan needs. Evolution between the plans is for further study. However, for new equipment, it is recommended that E.164 be adopted. .RT .sp 2P .LP \fB1\fR \fBNational numbering plan\fR .sp 1P .RT .PP 1.1 Each telephone Administration should give the most careful consideration to the preparation of a \fInational numbering plan\fR .FS See the CCITT manual cited in [1] for a comprehensive study of national numbering plans from the national point of view. .FE for its own network. This plan should be designed so that a subscriber is always called by the same number in the trunk service. It should be applicable to all incoming international calls. .sp 9p .RT .PP Administrations are strongly urged to advise the ITU or CCITT of national numbering plan changes well in advance of the event, so that this information can be published in the ITU \fIOperational Bulletin\fR . .sp 2P .LP 1.2 \fINumber analysis\fR .sp 1P .RT .PP 1.2.1 The national numbering plan of a country should be such that an analysis of a minimum number of digits of the national (significant) number (see definitions in Recommendation\ E.160): .sp 9p .RT .LP a) gives routing that reflects economic and other appropriate network factors; .LP b) indicates the charging area in those countries where there are several. .bp .PP 1.2.2 In the case of a country with a two\(hy or three\(hydigit country code, not more than two digits of the national (significant) number need be analyzed for these purposes. .PP In the case of a country with a one\(hydigit country code, not more than the three digits of the national (significant) number need be analyzed for these purposes. .PP 1.2.3 In the case where an integrated numbering plan covers a group of countries, the digit analysis specified in \(sc\ 1.2.2 should also determine the country of destination. .PP 1.2.4 For the requirements relating to frontier traffic, see Recommendation\ D.390\ R\ [2]. .sp 2P .LP \fB2\fR \fBLimitation of the\fR \fBnumber of digits to be dialled by\fR \fBsubscribers\fR .sp 1P .RT .sp 1P .LP 2.1 \fIInternational number\fR .sp 9p .RT .PP The CCITT recommended in 1964 that the number of digits to be dialled by subscribers in the automatic international service should not be more than\ 12 (excluding the international prefix). It is emphasized that this is the maximum number of digits and Administrations are invited to do their utmost to limit the digits to be dialled to the smallest possible number. .RT .sp 1P .LP 2.2 \fINational (significant) number\fR .sp 9p .RT .PP Noting that: .RT .LP a) the international number (excluding the international prefix) consists of the country code followed by the national (significant) number; .LP b) the smallest possible number of digits to be dialled in the automatic international service is achieved by limiting the number of digits of the country code and/or of the national (significant) number; .LP c) in some countries where telephony is already developed to an advanced stage, the national numbering plans in force enable the number of digits of the international number to be limited to less than\ 12; .LP d) some other countries which drew up their national numbering plans some time before 1964 have taken steps to ensure that the number of digits of the international number will not exceed\ 12 and may even be less; .LP the CCITT recommends that the number of digits of the national (significant) number should be equal to a maximum of 12\ \(em\ \fIn\fR , where \fIn\fR is the number of digits of the country code. .sp 2P .LP \fB3\fR \fBDigit capacity of international registers\fR .sp 1P .RT .PP The CCITT considers it advisable to recommend that the digit capacity of registers dealing with international traffic should allow for future conditions that may arise, but not possible to specify at the present time. In this regard, registers dealing with international traffic should have a digit capacity, or a capacity that can be expanded, to cater for more than the maximum 12\(hydigit international number envisaged at present. The increase in the number of digits above\ 12 is left as a matter of decision to be taken by individual Administrations. However, for new applications a minimum digit capacity of 15 digits is recommended (see Recommendation\ E.164). Administrations are recommended, when making such a decision, to take account of the new applications likely to be introduced in the international service, and which are now being studied by the CCITT. .RT .sp 2P .LP \fB4\fR \fBPrefixes and codes\fR .sp 1P .RT .sp 1P .LP See definitions in Recommendation\ E.160. .FE 4.1 \fIInternational prefix\fR .sp 9p .RT .PP It is recommended by the CCITT that the Administrations of countries that have not yet introduced automatic international operation, or Administrations that are, for various reasons, revising their numbering plans should adopt an international prefix (a code for access to the international automatic network) composed of the two digits\ 00. .bp .PP The reasons for this recommendation are: .RT .LP \(em to provide a maximum degree of standardization such that dialling is made as easy as possible for a person travelling in different countries (many countries already use the code\ 00), .LP \(em to minimize the number of digits to be dialled in automatic international operation, .LP \(em to simplify, for a future time when the use of the international prefix might have become a universal international standard, the format for writing an international telephone number. .sp 2P .LP 4.2 \fICountry code\fR \u,\d .FS A \*Qcountry code\*U may be assigned either to an individual country or to a geographical area. .FE .sp 1P .RT .PP 4.2.1 Country codes will be used: .sp 9p .RT .LP \(em in semi\(hyautomatic operation, to route calls to the required country when the calls are transit calls or when, on the outgoing positions, there is common dialling access to all the outgoing routes; .LP \(em in automatic operation. .PP 4.2.2 A list of country codes was prepared by the CCITT within the framework of a worldwide automatic telephone numbering plan. .PP This list was set up according to the following principles: .LP a) The number of digits of the country code is one, two or three according to the foreseeable telephonic and demographic development of the country concerned. .LP b) The nine digits from\ 1 to\ 9 have been allocated as the country code or as the first digit of the country code. These digits define \fIworld numbering zones\fR . .LP c) In the case of Europe, owing to the large number of countries requiring two\(hydigit codes, the two digits\ 3 and\ 4 have been allocated as the first digit of the country codes. .PP 4.2.3 The list of country codes already assigned is given in Annex\ A. .sp 2P .LP 4.3 \fIAssignment of country codes\fR .sp 1P .RT .PP 4.3.1 The existing world numbering plan should be maintained and codes presently assigned should not be changed, unless consolidation of an existing numbered area yields an advantage in terms of code usage. .sp 9p .RT .PP 4.3.2 All spare country codes will be assigned on a 3\(hydigit basis, as detailed in Annex\ B. The list of spare country codes for the international semiautomatic and automatic service is given in Annex\ C. .PP 4.3.3 In the case where all the country codes in a world numbering zone have been assigned and an additional code is required in that zone, a spare country code from another world numbering zone can be used in accordance with the following rules: .PP 4.3.3.1 Preference should be given to the assignment of a spare country code from an adjacent world numbering zone. .PP 4.3.3.2 If spare codes are not available from an adjacent world numbering zone, assignments will be made from the zones with the most spare codes. .sp 1P .LP 4.4 \fICodes for new international services\fR .sp 9p .RT .PP The introduction of some international services requires the allocation of a country code. In such cases, the assignment of a country code will be determined by the rules detailed in Annex\ B. .bp .RT .sp 2P .LP 4.5 \fITrunk prefix\fR .sp 1P .RT .PP 4.5.1 The \fInational (significant) number\fR | (see definition\ 8 of Recommendation\ E.160) does not include the trunk prefix. Accordingly, in the international service, the trunk prefix of the country of destination must not be dialled. .sp 9p .RT .PP It should be noted that, in some countries, it is customary to consider \fIfor national purposes\fR | that the trunk prefix is included in the national number [which is then not the national (significant) number]. A careful distinction must therefore be made between such national definition or practice and the CCITT definition, which is internationally valid. In order to avoid misunderstanding, the CCITT definition includes the word \*Qsignificant\*U between brackets, reading as follows: \*Qnational (significant) number\*U. .PP 4.5.2 It is recommended by the CCITT that the Administrations of countries that have not yet adopted a trunk prefix for access to their national automatic trunk network should adopt a prefix composed of a single digit, preferably\ 0. Irrespective of what digit is adopted as a trunk prefix, this digit should be precluded from being used also as a first digit of the trunk codes. .PP The reasons for this recommendation are: .LP \(em to provide the maximum degree of standardization of the trunk prefixes used in different countries, so that dialling is made as easy as possible for a person travelling from one country to another, .LP \(em to minimize the number of digits to be dialled in the automatic national service, .LP \(em to reduce user problems which arise because of the requirement, in automatic international operation, that the trunk prefix of the country of destination must not be dialled. .PP 4.5.3 In the automatic international service, following the international prefix and country code of the called country, the caller should dial the national (significant) number of the called subscriber (i.e.\ without dialling the trunk prefix). .PP 4.5.4 The use and printing of symbols and separators in national and international telephone numbers is detailed in Recommendation\ E.123. .sp 1P .LP 4.6 \fIUse of zero as an\fR \fIescape code\fR .sp 9p .RT .PP The use of the digit \*Q0\*U (zero) as an escape code for numbering plan interworking is described in Recommendation\ E.166. .RT .LP .sp 2 .ce 1000 ANNEX\ A .ce 0 .ce 1000 (to Recommendation E.163) .sp 9p .RT .ce 0 .ce 1000 \fBList of country codes\fR \fB incorporating amendments proposed\fR .sp 1P .RT .ce 0 .ce 1000 \fBby the World Plan Committee, 1988\fR .ce 0 .sp 1P .ce 1000 \fBWorld numbering ZONE 1\fR .ce 0 .sp 1P .ce 1000 2 col .ce 0 .LP Anguilla 1 | ua\d\u)\d .LP Canada 1 | ua\d\u)\d .LP United\ States\ of\ America,\ including .LP \ \ Puerto\ Rico\ and\ the\ Virgin\ Islands 1 | ua\d\u)\d .LP Jamaica 1 | ua\d\u)\d .LP Barbados 1 | ua\d\u)\d .LP Antigua and Barbuda 1 | ua\d\u)\d .LP Cayman\ Islands 1 | ua\d\u)\d .LP British\ Virgin\ Islands 1 | ua\d\u)\d .LP Bermuda 1 | ua\d\u)\d .LP Bahamas (Commonwealth of the) 1 | ua\d\u)\d .LP Dominican Republic 1 | ua\d\u)\d .LP Grenada 1 | ua\d\u)\d .LP Montserrat 1 | ua\d\u)\d .LP Saint Kitts and Nevis 1 | ua\d\u)\d .LP Saint Lucia 1 | ua\d\u)\d .LP Saint Vincent and the Grenadines 1 | ua\d\u)\d .LP Turks and Caicos (Islands) 1 | ua\d\u)\d .LP \ua\d\u)\d Integrated numbering area. .bp .LP .PS 10 .sp 1P .ce 1000 \fBWorld numbering ZONE 2\fR .ce 0 .sp 1P .ce 1000 2 col .ce 0 .LP Egypt\ (Arab\ Republic\ of) \ 20 .LP Morocco\ (Kingdom\ of) \ 21 | ua\d\u)\d .LP Algeria\ (People's\ Democratic .LP \ \ Republic of) \ 21 | ua\d\u)\d .LP \fR Tunisia \ 21 | ua\d\u)\d .LP Libya\ (Socialist\ People's Libyan .LP \ \ Arab\ Jamahiriya) \ 21 | ua\d\u)\d .LP Gambia\ (Republic\ of\ the) 220 .LP Senegal\ (Republic\ of) 221 .LP Mauritania\ (Islamic\ Republic\ of) 222 .LP Mali\ (Republic\ of) 223 .LP Guinea\ (Republic\ of) 224 .LP C\* | te\ d'Ivoire\ (Republic\ of) 225 .LP Burkina\ Faso 226 .LP Niger\ (Republic\ of\ the) 227 .LP Togolese\ Republic 228 .LP Benin\ (People's\ Republic\ of) 229 .LP Mauritius 230 .LP Liberia\ (Republic\ of) 231 .LP Sierra\ Leone 232 .LP Ghana 233 .LP Nigeria\ (Federal\ Republic\ of) 234 .LP Chad\ (Republic\ of) 235 .LP Central\ African\ Republic 236 .LP Cameroon\ (Republic\ of) 237 .LP Cape\ Verde\ (Republic\ of) 238 .LP Sao\ Tome\ and\ Principe .LP \ \ Democratic\ Republic\ of) 239 .LP Equatorial\ Guinea\ (Republic\ of) 240 .LP Gabonese Republic 241 .LP Congo (People's Republic of the) 242 .LP Zaire (Republic of) 243 .LP Angola (People's Republic of) 244 .LP Guinea\(hyBissau (Republic of) 245 .LP Diego Garcia 246 .LP Ascension 247 .LP Seychelles (Republic of) 248 .LP Sudan (Republic of the) 249 .LP Rwandese Republic 250 .LP Ethiopia 251 .LP Somali Democratic Republic 252 .LP Djibouti (Republic of) 253 .LP Kenya (Republic of) 254 .LP Tanzania (United Republic of) 255 .LP Uganda (Republic of) 256 .LP Burundi (Republic of) 257 .LP Mozambique (People's Republic of) 258 .LP Zanzibar (Tanzania) 259 .LP Zambia (Republic of) 260 .LP Madagascar (Democratic Republic of) 261 .LP Reunion (French Department of) 262 .LP Zimbabwe (Republic of) 263 .LP Namibia 264 .LP Malawi 265 .LP Lesotho (Kingdom of) 266 .LP Botswana (Republic of) 267 .LP Swaziland (Kingdom of) 268 .LP Comoros (Islamic Federal .LP \ \ Republic of the) 269 .LP South Africa (Republic of) \ 27 .LP San\ Marino\ (Republic\ of) 295 .LP Trinidad\ and\ Tobago 296 .LP Aruba 297 .LP Faroe Islands (Denmark) 298 .LP Greenland (Denmark) 299 \v'3p' .LP \fISpare\ codes\fR .LP 280, 281, 282, 283, 284, 285, 286, 287, 288, 289 .LP 290, 291, 292, 293, 294, .LP \ua\d\u)\d \fIIntegrated numbering area with subdivisions:\fR .LP \(em\ Morocco:\ 210, 211, 212 (212 in service); .LP \(em\ Algeria:\ 213, 214, 215; .LP \(em\ Tunisia:\ 216, 217; .LP \(em\ Libya:\ 218, 219. .LP .PS 10 .sp 1P .ce 1000 \fBWorld numbering ZONES 3 and 4\fR .ce 0 .sp 1P .ce 1000 2 col .ce 0 .LP Greece \ 30 .LP Netherlands\ (Kingdom\ of\ the) \ 31 .LP Belgium \ 32 .LP France \ 33 | ua\d\u)\d .LP Monaco \ 33 | ua\d\u)\d .LP Spain \ 34 .LP Gibraltar 350 .LP Portugal 351 .LP Luxembourg 352 .LP Ireland 353 .LP Iceland 354 .LP Albania (Socialist People's Republic of) 355 .LP Malta (Republic of) 356 .LP Cyprus (Republic of) 357 .LP Finland 358 .LP Bulgaria (People's Republic of) 359 .LP \ua\d\u)\d Integrated numbering plan. .bp .LP Hungarian\ People's\ Republic 36 .LP German\ Democratic\ Republic 37 .LP Yugoslavia\ (Socialist\ Federal\ Republic\ of) 38 .LP Italy 39 .LP Romania\ (Socialist\ Republic\ of) 40 .LP Switzerland\ (Confederation\ of) 41\ua\d\u)\d .LP Liechtenstein\ (Principality\ of) 41\ua\d\u)\d .LP Czechoslovak\ Socialist\ Republic 42 .LP Austria 43 .LP United\ Kingdom\ of\ Great\ Britain\ and .LP \ \ Northern\ Ireland 44 .LP Denmark 45 .LP Sweden 46 .LP Norway 47 .LP Poland (People's Republic of) 48 .LP Germany (Federal Republic of) 49 .LP .rs .sp 1P .ad r BLANC .ad b .RT .LP \ua\d\u)\d Integrated numbering plan. .LP .PS 10 .bp .sp 1P .ce 1000 \fBWorld numbering ZONE 5\fR .ce 0 .sp 1P .ce 1000 2 col .ce 0 .LP Falkland Islands (Malvinas) 500 .LP Belize 501 .LP Guatemala\ (Republic\ of) 502 .LP El\ Salvador\ (Republic\ of) 503 .LP Honduras\ (Republic\ of) 504 .LP Nicaragua 505 .LP Costa\ Rica 506 .LP Panama\ (Republic\ of) 507 .LP St. Pierre and Miquelon (French Department of) 508 .LP Haiti\ (Republic\ of) 509 .LP Peru \ 51 .LP Mexico \ 52 .LP Cuba \ 53 .LP Argentine\ Republic \ 54 .LP Brazil (Federative\ Republic\ of) \ 55 .LP Chile \ 56 .LP Colombia (Republic of) \ 57 .LP Venezuela (Republic of) \ 58 .LP Guadeloupe (French Department of) 590 .LP Bolivia (Republic of) 591 .LP Guyana 592 .LP Ecuador 593 .LP Guiana (French Department of) 594 .LP Paraguay (Republic of) 595 .LP Martinique (French Department of) 596 .LP Suriname (Republic of) 597 .LP Uruguay (Eastern Republic of) 598 .LP Netherlands Antilles 599 \v'1p' .sp 1P .ce 1000 \fBWorld numbering ZONE 6\fR .ce 0 .sp 1P .ce 1000 2 col .ce 0 .LP Malaysia \ 60 .LP Australia \ 61 .LP Indonesia\ (Republic\ of) \ 62 .LP Philippines\ (Republic\ of\ the) \ 63 .LP New\ Zealand \ 64 .LP Singapore\ (Republic\ of) \ 65 .LP Thailand \ 66 .LP Mariana Islands 670 .LP Guam 671 .LP Australian External Territories 672 .LP Brunei Darussalam 673 .LP Nauru\ (Republic\ of) 674 .LP Papua\ New\ Guinea 675 .LP Tonga\ (Kingdom\ of) 676 .LP Solomon Islands 677 .LP Vanuatu\ (Republic\ of) 678 .LP Fiji 679 .LP Palau 680 .LP Wallis and Futuna Islands 681 .LP Cook Islands 682 .LP Niue Island 683 .LP American Samoa 684 .LP Western Samoa (Independent State of) 685 .LP Kiribati (Republic of) 686 .LP New Caledonia and Dependencies 687 .LP Tuvalu 688 .LP French Polynesia 689 .LP Tokelan 690 .LP F.S. of Micronesia 691 .LP Marshall Islands 692 \v'3p' .LP \fISpare codes\fR 693, 694, 695, 696, 697, 698, 699 .LP .PS 10 .sp 1P .ce 1000 \fBWorld numbering ZONE 7\fR .ce 0 .sp 1P .ce 1000 Union of Soviet Socialist Republics\ \ 7 .ce 0 .sp 1P .ce 1000 \fBWorld numbering ZONE 8\fR .ce 0 .sp 1P .ce 1000 2 col .ce 0 .LP Japan \ 81 .LP Korea\ (Republic\ of) \ 82 .LP Viet\ Nam\ (Socialist\ Republic\ of) \ 84 .LP Democratic People's Republic of Korea 850 .LP Hong\(hyKong 852 .LP Macao 853 .LP Democratic Kampuchea 855 .LP Lao People's Democratic Republic 856 .LP China (People's Republic of) \ 86 | ua\d\u)\d .LP Maritime Mobile Service \ 87 | ub\d\u)\d .LP Bangladesh (People's Republic of) 880 | uc\d\u)\d \v'3p' .LP \fISpare\ codes\fR 800, 801, 802, 803, 804, 805, 806, 807, 808, 809 .LP 830, 831, 832, 833, 834, 835, 836, 837, 838, 839 .LP 851, 854, 857, 858, 859 .LP 890, 891, 892, 893, 894, 895, 896, 897, 898, 899 .LP \ua\d\u)\d Within this national code, the Telecommunications Administration of the People's Republic of China has notified that the code\ 866 has been allocated to the province of Taiwan. (Reference: Notification No. 1157 of 10 December 1980.) .LP \ub\d\u)\d The country code 87 is reserved for the Maritime Mobile Service. The following three digit country codes are assigned:\ 871 INMARSAT (Atlantic), 872 INMARSAT (Pacific), 873 INMARSAT (Indian Ocean). .LP \uc\d\u)\d The remaining combinations in series 88 will not be allocated until the stock of spare 3\(hydigit codes for the region is exhausted. .bp .LP .PS 10 .sp 1P .ce 1000 \fBWorld numbering ZONE 9\fR .ce 0 .sp 1P .ce 1000 2 col .ce 0 .LP Turkey \ 90 .LP India\ (Republic\ of) \ 91 .LP Pakistan\ (Islamic\ Republic\ of) \ 92 .LP Afghanistan\ (Democratic\ Republic\ of) \ 93 .LP Sri\ Lanka\ (Democratic .LP \ \ Socialist\ Republic\ of) \ 94 .LP Burma\ (Socialist\ Republic .LP \ \ of\ the\ Union\ of) \ 95 .LP Maldives\ (Republic\ of) 960 .LP Lebanon 961 .LP Jordan\ (Hashemite\ Kingdom\ of) 962 .LP Syrian\ Arab\ Republic 963 .LP Iraq\ (Republic\ of) 964 .LP Kuwait (State of) 965 .LP Saudi Arabia (Kingdom of) 966 .LP Yemen Arab Republic 967 .LP Oman (Sultanate of) 968 .LP Yemen (People's .LP \ \ Democratic Republic of) 969 .LP United Arab Emirates | ua\d\u)\d 971 .LP Israel (State of) 972 .LP Bahrain (State of) 973 .LP Qatar (State of) 974 .LP Kingdom of Bhutan 975 .LP Mongolian People's Republic 976 .LP Nepal 977 .LP Iran \ 98 \v'3p' .LP \fISpare codes\fR 970, 978, 979 .LP 990, 991, 992, 993, 994, 995, 996, 997, 998, 999 .LP \ua\d\u)\d E.A.U: Abu Dhabi, Ajman, Dubai, Fujeirah, Ras Al Khaimah, Sharjah, Umm Al Qaiwain. \v'2P' .LP .PS 10 .ce 1000 ANNEX\ B .ce 0 .ce 1000 (to Recommendation E.163) .sp 9p .RT .ce 0 .ce 1000 \fBRules for the\fR \fBassignment of spare country codes\fR .sp 1P .RT .ce 0 .PP The rules listed in this annex are provided as a basis for the most effective utilization of the spare country codes. .sp 1P .RT .PP B.1 Single isolated 3\(hydigit codes should be assigned prior to the assignment of any 3\(hydigit code which is part of a series of more than two consecutive 3\(hydigit codes. .sp 1P .RT .PP B.2 The assignment of spare codes of a zone, both within that zone and also to another zone, will take place as follows: .sp 9p .RT .LP a) When assigning a code to a country in the same zone: .LP \fR start with the lowest numbered 3\(hydigit codes in ascending order, e.g.\ 670, 680,\ . | | .LP b) When assigning a code to a country in another zone: .LP start with the highest numbered 3\(hydigit codes in descending order, e.g.\ 688, 685,\ . | | .LP c) Within code 87 reserved for the Maritime Mobile Service a third digit will be assigned to codes used for maritime satellite ocean area systems, with the restriction that codes\ 878 and\ 879 may not be touched because they are reserved for national purposes. .PP B.3 Country codes for new international services or for the automation of some existing services should be taken from the world numbering zone with the most spare codes. .bp .sp 9p .RT .ce 1000 ANNEX\ C .ce 0 .ce 1000 (to Recommendation E.163) .sp 9p .RT .ce 0 .ce 1000 \fBList of spare country codes for the international\fR .sp 1P .RT .ce 0 .ce 1000 \fBsemiautomatic and automatic service\fR .ce 0 .LP \fISpare\ codes\fR | .sp 1P .RT .LP 280, 281, 282, 283, 284, 285, 286, 287, 288, 289 .LP 290, 291, 292, 293, 294, .LP 693, 694, 695, 696, 697, 698, 699 .LP 800, 801, 802, 803, 804, 805, 806, 807, 808, 809 .LP 830, 831, 832, 833, 834, 835, 836, 837, 838, 839 .LP 851, 854, 857, 858, 859 .LP 890, 891, 892, 893, 894, 895, 896, 897, 898, 899 .LP 970, 978, 979 .LP 990, 991, 992, 993, 994, 995, 996, 997, 998, 999 .sp 2P .LP \fBReferences\fR .sp 1P .RT .LP [1] CCITT manual \fINational telephone networks for the automatic\fR \fIservice\fR , ITU, Geneva, 1964, 1968, 1978. .LP [2] CCITT Recommendation \fIAccounting system in the international\fR \fIautomatic telephone service\fR , Rec.\ D.390\ R. \v'1P' .sp 2P .LP \fBRecommendation E.164\fR .FS This Recommendation appears in the Series I Recommendations as Recommendation\ I.331 (Fascicle\ III.8). .FE .RT .sp 2P .sp 1P .ce 1000 \fBNUMBERING\ PLAN\ FOR\ THE\ ISDN\ ERA\fR .EF '% Fascicle\ II.2\ \(em\ Rec.\ E.164'' .OF '''Fascicle\ II.2\ \(em\ Rec.\ E.164 %' .ce 0 .sp 1P .LP \fB1\fR \fBIntroduction\fR .sp 1P .RT .PP The rapid advances in telecommunications technology coupled with increased diversification of customer demands served by a number of different types of dedicated public switched networks (telephone, telex, data,\ etc.) have created a need to provide a uniform customer access and network structure. Such a structure is called the Integrated Services Digital Network (ISDN). Implementation of ISDNs have begun in a number of countries and eventually these will carry all existing and new services. .PP To facilitate ISDN evolution internationally, this Recommendation defines the numbering arrangements for an ISDN. The timetable for implementation of this numbering plan is described in Recommendation\ E.165. .RT .sp 2P .LP \fB2\fR \fBDefinitions\fR .sp 1P .RT .PP Within the integrated service environment, the terms used for all networks and services must be compatible and consistent. A list of terms and their definitions relating to numbering are contained in Recommendation\ E.160. .RT .LP .sp 1 .bp .sp 2P .LP \fB3\fR \fBISDN numbering plan principles\fR .sp 1P .RT .sp 1P .LP 3.1 \fIGeneral\fR .sp 9p .RT .PP The ISDN numbering and addressing principles are described in Recommendation\ I.330. The ISDN numbering plan will be based on and evolve from the existing numbering plans applicable to national and international public telephone networks. .PP In view of the evolutionary nature of ISDN, the international numbering plan should provide for substantial capacity to accommodate future network requirements. .RT .PP Country or geographical area. .FE Where multiple destinations (i.e., RPOAs/networks) serve the called party's geographic area, the national ISDN numbering arrangement in the country of destination shall provide for discrimination between these RPOAs/networks. The procedure for discrimination between multiple transit\(hyRPOAs/networks is not considered to be a destination address requirement and shall therefore be excluded from the ISDN numbering arrangements. .PP Before the ISDN numbering arrangement attains global penetration, it must allow for interworking between the ISDN and other public networks. Such arrangements are discussed in Recommendation\ E.166. Interworking with private networks shall also be taken into account. The definition of private networks and the methods of interworking are for further study and will be covered in future Series\ E Recommendations. .PP The 10\ digit decimal character set\ 0\(hy9 is used throughout the ISDN numbering plan format including subscriber number, national (significant) number and the country code. .PP Prefixes and other information concerned with identifying selection procedures or network service parameters (such as quality of service or transit delay) do not form part of the ISDN number. .PP The ISDN numbering plan shall include an unambiguous identification of a particular country . In addition, the ISDN number will identify networks and/or ISDNs within these countries , if required. In doing so, it shall retain the integrity of the telephone country code as defined in Recommendations\ E.160 and\ E.163. .RT .sp 1P .LP 3.2 \fIStructure of the international ISDN number\fR .sp 9p .RT .PP The international ISDN number is composed of a variable length of decimal digits arranged in specific code fields. The international ISDN number code fields are the country code (CC) and the national (significant) number. .PP The country code (CC) is used to select the destination country and varies in length as outlined in Recommendation\ E.163. .PP The national (significant) number N(S)N is used to select the destination subscriber. In selecting the destination subscriber, however, it may be necessary to select a destination network. To accomplish this selection, the national (significant) number N(S)N code field comprises a national destination code (NDC) followed by the subscribers number (SN). .PP The NDC field will be variable in length depending upon the requirements of the destination country. Each NDC may have one of the following structures: .RT .LP a) a Destination Network (DN) code, which can be used to select a destination network serving the destination subscribers; .LP b) a Trunk Code (TC), the format of which is defined in Recommendation\ E.160; .LP c) any combination of Destination Network (DN) code and Trunk Code (TC). .PP The NDCs of an Administration may consist of any of the above structures. .PP \fINote\fR \ \(em\ The sequences DN\(hyTC and TC\(hyDN are a national matter. This is a subject for further study. .bp .PP The subscriber's number (SN) varies in length depending on the requirements of the destination country and is in accordance with Recommendation\ E.160. .PP Figure\ 1/E.164 shows the number structure. .PP Where appropriate, identification of an ISDN within the destination country shall be through the use of a national destination code (NDC) incorporated in the ISDN number. .RT .LP .rs .sp 16P .ad r \fBFigure 1/E.164, p.\fR .sp 1P .RT .ad b .RT .sp 1P .LP 3.3 \fINumber length\fR .sp 9p .RT .PP The international number may be of variable length. The maximum number length shall be 15\ digits. However, some Administrations may wish to increase their register capacity to 16\ or 17\ digits. The decision on register capacity is left as a matter to be taken by individual Administrations. .PP The length does not include prefixes, language digit , address delimiters (e.g.,\ end of pulsing signals,\ etc.) since these items are not considered as part of the international ISDN number. .RT .sp 1P .LP 3.4 \fINumber analysis\fR .sp 9p .RT .PP In order to determine: .RT .LP \(em the country of destination, .LP \(em the most appropriate network routing, .LP \(em the proper charging, .LP the originating country must analyse a number of digits of the international number. The national destination code (NDC) increases the potential requirement for number analysis because it provides for a combination of either a trunk code (TC) and/or a network identification function. Careful consideration should be given to the preparation of the national destination code (NDC) assignments. .PP On international calls the number analysis performed at the originating country need not be more than the country code and: .LP \(em three digits of the NSN in the case of a country with a three digit country code, .LP \(em four digits of the NSN in the case of a country with a two digit country code, .LP \(em five digits of the NSN in the case of a country with a one digit country code. .PP (Translation beyond this requirement could be arranged by bilateral agreement if required, e.g.,\ countries assigned a 1\ digit country code may require analysis of up to 6\ digits beyond the country code.) .bp .sp 2P .LP \fB4\fR \fBNumber allocation principles\fR .sp 1P .RT .PP The assignment of country codes is administered by the CCITT, while NSN (NDC plus SN) code assignments are a national responsibility. .PP ISDN subscriber numbers may be allocated from the range of subscriber numbers available in the local ISDN exchange. These will be assigned to customers who subscribe only to the telephone service, customers with one or more data services and customers with a mixture of telephony and data services. .PP Subscribers equipped with basic access (the definition of ISDN basic access is given in the Series\ I Recommendations) should normally be allocated one unique number. .RT .sp 2P .LP \fB5\fR \fBNetwork identification\fR .sp 1P .RT .PP In countries served by more than one ISDN and/or Public Switched Telephone Network (PSTN) the network identification of each is a national matter. .PP Network identification within the national (significant) number shall be such that: .RT .LP \(em in a country all destination ISDN and PSTN networks shall operate under a single Recommendation\ E.163 country code, .LP \(em the international number maximum length of 15\ digits shall not be exceeded, nor shall it be necessary for the number of digits for number analysis to exceed that specified in \(sc\ 3.4, .LP \(em provision of network identification is not mandatory for countries using a single integrated numbering plan arrangement for their ISDNs and PSTNs. .sp 2P .LP \fB6\fR \fBService identification\fR .sp 1P .RT .PP The ISDN number by itself will not identify the particular nature of the service, type of connection or quality of service required. An indication of parameters describing the service required by the calling terminal will be included in a service identifier in the signalling information. This service identifier is not considered to be part of the numbering plan. .RT .sp 2P .LP \fB7\fR \fBCalling/called line identity\fR .FS This termiminology needs further study. .FE .sp 1P .RT .PP Calling/called line identity (CLI/CDLI) is address information which is passed across the network to provide supplementary services such as calling (or called) line identification presentation. The format of the CLI and CDLI for international calls should be the full international number, i.e.,\ Country Code (CC), National Destination Code (NDC) and Subscriber Number (SN). No other information, such as prefixes or symbols (e.g.\ \*Q+\*U), should be included, although a subaddress may be associated with the CLI/CDLI. .RT .sp 2P .LP \fB8\fR \fBDialling procedures\fR .sp 1P .RT .PP The subscriber dialling procedures for local, national and international calls shall be in accordance with Recommendation\ E.163. However, subscribers' control procedures for supplementary services will be as defined in Recommendation\ E.131 or in separate Recommendations for each service. .PP ISDN subscribers will always be called by the same subscriber number irrespective of where in the network the call originates. For calls in the same numbering area or local network the subscriber number alone is dialled. For national calls between numbering areas or local networks the subscriber number may be preceded by the national prefix and the national destination code. .PP The addressing procedures for calls using sub\(hyaddressing are described in \(sc\ 11. .bp .RT .sp 2P .LP \fB9\fR \fBPrefixes\fR .sp 1P .RT .PP The use of prefixes shall be in accordance with Recommendations\ E.160, E.163 and E.166. Where necessary, prefixes can also be used for network and service selection. .RT .sp 2P .LP \fB10\fR \fBEscape code\fR .sp 1P .RT .PP The use of the digit \*Q0\*U as an escape code for numbering plan interworking is described in Recommendation\ E.166. .RT .sp 2P .LP \fB11\fR \fBAddress information\fR .sp 1P .RT .PP Identification within a subscriber's installation of a point beyond that defined by the ISDN number requires the transfer of address information from the public network to the subscriber's equipment. The following methods apply: .RT .sp 1P .LP 11.1 \fIDirect dialling\(hyin\fR .sp 9p .RT .PP With direct\(hydialling\(hyin (DDI) the last few digits forming the end of the ISDN subscriber number are transferred to the called subscriber's installation (see Figure\ 2/E.164). The number of digits used varies and depends upon the requirements of the called subscriber's equipment and the capacity of the numbering plan used. .PP ISDN subscriber numbers used for DDI may be those published in the public directory. .RT .LP .rs .sp 13P .ad r \fBFigure 2/E.164, p. .sp 1P .RT .ad b .RT .sp 1P .LP 11.2 \fISub\(hyaddressing (network address extension)\fR .sp 9p .RT .PP Sub\(hyaddressing provides a separate additional addressing capacity outside the ISDN numbering plan but constitutes an intrinsic part of the ISDN addressing capabilities. As shown in Figure\ 2/E.164, up to 20\ octets (or 40\ digits) may follow the ISDN number and form the ISDN sub\(hyaddress, which is transferred to the equipment at the subscriber's premises. .PP When required, the sub\(hyaddress is sent by the calling party within the call set\(hyup procedure and is passed transparently through the network as a separate entity from both the ISDN number and user\(hyto\(hyuser information. Sub\(hyaddress information is not required to be processed within the public network. .PP Sub\(hyaddressing procedures are the subject of a separate Recommendation. .RT .sp 1P .LP 11.3 \fICombination of sub\(hyaddressing and direct dialling\(hyin\fR .sp 9p .RT .PP Sub\(hyaddressing may be used separately or in combination with DDI (see Figure 2/E.164). .bp .RT .sp 1P .LP 11.4 \fIAddress delimiters\fR .sp 9p .RT .PP DDI address information may contain an \*Qend of address\*U (e.g.,\ ST) delimiter. In the case of sub\(hyaddressing, an \*Qend of subscriber number/beginning of sub\(hyaddress\*U delimiter and the \*Qend of address\*U delimiter are required. .PP (The use of an address delimiter at the end of an ISDN address is for further study.) .RT .sp 2P .LP \fBRecommendation\ E.165\fR .RT .sp 2P .ce 1000 \fBTIMETABLE\ FOR\ COORDINATED\ IMPLEMENTATION\ OF\ THE\ FULL\ CAPABILITY\fR .EF '% Fascicle\ II.2\ \(em\ Rec.\ E.165'' .OF '''Fascicle\ II.2\ \(em\ Rec.\ E.165 %' .ce 0 .sp 1P .ce 1000 \fBOF\ THE\ NUMBERING\ PLAN\ FOR\ THE\ ISDN\ ERA\ (RECOMMENDATION\ E.164)\fR .ce 0 .sp 1P .LP \fB1\fR \fBIntroduction\fR .sp 1P .RT .PP Recommendation I.330 describes ISDN numbering and addressing principles, while Recommendation\ E.164 describes the numbering plan for the ISDN era. Recommendation\ E.164 also identifies the need for interworking arrangements between ISDN and present dedicated networks. .PP This Recommendation sets a specific time (Time \fIT\fR ), after which all ISDNs and PSTNs can use the full capability of Recommendation\ E.164, \*QNumbering plan for the ISDN era\*U, and identifies the numbering requirements on ISDNs and on dedicated networks intending to interwork with ISDNs, before and after Time\ \fIT\fR . .PP Among the significant principles which form the basis for this Recommendation, the following are considered especially useful for ready reference: .RT .LP \(em An E.163/E.164 telephony subscriber may become an ISDN subscriber without a number change. .LP \(em Numbers according to Recommendation E.164 apply to both PSTN and ISDN subscribers in the ISDN era. A mixture of PSTN and ISDN terminations on the same exchange is allowed. .LP \(em E.164 numbering arrangements may be used to distinguish between ISDN and PSTN subscribers. This is not necessary but is allowed, provided that possible effects on routing and digit analysis remain within the limits of Recommendation\ E.164. .sp 2P .LP \fB2\fR \fBApplication and evolution of Time \fI\fBT\fR .sp 1P .RT .PP ISDNs are expected to interwork with dedicated networks. However, due to the different addressing capabilities between the ISDN and existing numbering plans, some temporary constraints need to be imposed on the number length and digit analysis required to access the user network interfaces of the ISDNs before Time\ \fIT\fR . .RT .sp 2P .LP 2.1 \fINumbering constraints before Time T\fR .sp 1P .RT .sp 1P .LP 2.1.1 \fIISDNs\fR \fIinterworking with dedicated networks\fR .sp 9p .RT .PP To allow numbering plan interworking with dedicated networks before Time\ \fIT\fR , an ISDN will not assign international E.164 numbers longer than 12\ digits to its user network interfaces capable of receiving calls from dedicated networks. .PP In addition, for ISDNs and PSTNs, digit analysis as defined in Recommendation\ E.163 will apply. .RT .sp 1P .LP 2.1.2 \fIISDNs which do not interwork with dedicated networks\fR .sp 9p .RT .PP These ISDNs are allowed to assign numbers to user network interfaces according to the full capability of the numbering plan for the ISDN era. .PP Digit analysis according to Recommendation E.164 may be required to access user network interfaces connected to these networks. .bp .RT .sp 1P .LP 2.2 \fIEvolution after Time t\fR .sp 9p .RT .PP After Time\ \fIT\fR , ISDNs and PSTNs can make use of the full capability of E.164 numbers to identify their user network interfaces and terminals respectively. In addition, for routing purposes, the ISDNs and PSTNs conforming to Recommendation\ E.164 must be capable of analysing the ISDN international number to the extent required in that Recommendation. .PP \fINote\fR \ \(em\ Digit analysis for other dedicated networks is for further study. .RT .sp 2P .LP \fB3\fR \fBDate of Time \fI\fBT\fR .sp 1P .RT .PP The date for Time\ \fIT\fR has been set for 31 December 1996 at 23h59m Coordinated Universal Time UTC). .RT .sp 2P .LP \fB4\fR \fBNetwork requirements at Time \fI\fBT\fR .sp 1P .RT .PP ISDNs and PSTNs supporting number length and digit analysis as described in Recommendation\ E.164 are said to be \*QE.164\(hyconforming\*U networks. .PP All ISDNs must be E.164\(hyconforming networks. Functions associated with E\(hy164\(hyconforming networks are: .RT .LP a) for calls originated within such a network, provision for carrying E.164\ numbers of up to 15\ digits to interfacing networks; .LP b) comparable treatment for transit calls; .LP c) capability for conducting digit analysis for ISDNs and PSTNs as indicated in Recommendation\ E.164; .LP d) screening to ensure that, taking into account agreements between the networks concerned, no transit calls are offered to non\(hyconforming networks incapable of handling number lengths as defined in Recommendation\ E.164; .LP e) provision of interim procedures, such as two\(hystage selection, for internal network sources, e.g.,\ local exchanges, not equipped to handle 15\ digits, so that all internal network sources can originate calls to all E.164 addresses. .PP \fINote\ 1\fR \ \(em\ Other requirements on conforming networks are for further study. Non\(hyconforming networks may seek bilateral agreements with conforming networks, or adopt intra\(hynetwork procedures to provide means by which subscribers of the non\(hyconforming networks may originate calls to subscribers connected to ISDNs and PSTNs requiring a number length or analysis in excess of the capabilities of the non\(hyconforming network. .PP \fINote\ 2\fR \ \(em\ Limitations of non\(hyconforming networks and interworking procedures are for further study. .RT .sp 2P .LP \fBRecommendation\ E.166\fR .RT .sp 2P .sp 1P .ce 1000 \fBNUMBERING\ PLAN\ INTERWORKING\ IN\ THE\ ISDN\ ERA\fR .EF '% Fascicle\ II.2\ \(em\ Rec.\ E.166'' .OF '''Fascicle\ II.2\ \(em\ Rec.\ E.166 %' .ce 0 .sp 1P .LP \fB1\fR \fBIntroduction\fR .sp 1P .RT .PP 1.1 Numbering plan interworking is a fundamental requirement for successful completion of calls routed between networks using different numbering plans, e.g.,\ calls routed between an ISDN using the Recommendation\ E.164 numbering plan and a public data network (PDN) using the X.121 numbering plan. .sp 1P .RT .PP 1.2 This Recommendation is one of a set of CCITT Recommendations that address numbering plan interworking procedures for calls between terminals connected to an ISDN and terminals connected to a dedicated network. The term \*Qdedicated network\*U in the context of this Recommendation includes: public switched telephone network (PSTN), packet switched public data network (PSPDN), circuit switched public data network (CSPDN) and telex network. .bp .PP 1.3 This Recommendation is related to and is compatible with the following Recommendations: .LP \(em Rec.\ E.160: Definitions relating to national and international numbering plans .LP \(em Rec.\ E.163: Numbering plan for the international telephone service .LP \(em Rec.\ E.164: Numbering plan for the ISDN era .LP \(em Rec.\ E.165: Timetable for coordinated implementation of the full capability of the numbering plan for the ISDN era .LP \(em Rec.\ F.69: Plan for telex destination codes .LP \(em Rec.\ I.330: ISDN numbering and addressing principles .LP \(em Rec.\ I.332: Numbering principles for interworking between ISDNs and dedicated networks with different numbering plans .LP \(em Rec.\ Q.931: ISDN user\(hynetwork interface layer\ 3 specification .LP \(em Rec.\ Q.761\(hyQ.764: Signalling System No.\ 7 \(em ISDN User Part .LP \(em Rec.\ U.202: Requirements to be met in providing telex service within the ISDN .LP \(em Rec.\ X.121: International numbering plan for public data networks .LP \(em Rec.\ X.122: Numbering plan interworking between a packet switched public data network (PSPDN) and an integrated services digital network (ISDN) or public switched telephone network (PSTN) in the short\(hyterm .sp 2P .LP \fB2\fR \fBScope\fR .sp 1P .RT .PP 2.1 The scope and application of this Recommendation includes the following numbering plan interworking and address signalling scenarios indicated in Figure\ 1/E.166, i.e.,\ interworking for calls from an ISDN terminal to: .sp 9p .RT .LP a) an ISDN terminal on another ISDN to provide an ISDN service as defined in the I\(hy200 Series of Recommendations; .LP b) a voice terminal on a PSTN, for voice services; .LP c) a data terminal on a PSTN, for voice\(hyband data services; .LP d) a data terminal on a PSPDN, for packet switched data services; .LP e) a data terminal on a CSPDN, for circuit switched data services; .LP f ) a telex terminal on a telex network, for telex services defined in Recommendation\ F.60. .PP 2.2 The term \*QISDN terminal\*U is used here in a generic sense, i.e.,\ an integrated terminal that can support one or more services as per the I\(hy200 Series Recommendations using the Q.931 protocol, and may include the services provided by the dedicated networks under cases\ b) to\ f ) above. This functionality may be provided by using appropriate existing terminals with terminal adaptors (TA) supporting requisite protocols, e.g.,\ an X.25 terminal with a TA supporting protocol defined by Recommendation\ X.31/I.462 for packet switched data services. .PP 2.3 The following interworking cases need to be considered, based on the terminal/TA combinations on the originating and destination networks: .LP a) calls from a speech terminal on ISDN to: .LP \(em a speech terminal on another ISDN, .LP \(em a voice terminal on a PSTN. .LP b) calls from an X.25 terminal on an ISDN to: .LP \(em an X.25 terminal on another ISDN, .LP \(em an X.25 terminal on a PSPDN, .LP \(em an X.25 terminal on a PSTN, .LP \(em an X.25 terminal on a CSPDN, .LP \(em a telex terminal on a telex network. .bp .LP .rs .sp 38P .ad r \fBFigure 1/E.166, p.8\fR .sp 1P .RT .ad b .RT .LP c) calls from an X.21 terminal on an ISDN to: .LP \(em an X.21 terminal on another ISDN, .LP \(em an X.21 terminal on a CSPDN. .LP d) calls from a voice\(hyband data terminal on an ISDN to: .LP \(em a voice\(hyband data terminal on another ISDN, .LP \(em a voice\(hyband data terminal on a PSTN. .LP e) calls from a telex terminal on an ISDN to: .LP \(em a telex terminal on a telex network. .bp .PP 2.4 The primary focus of this Recommendation is to specify the numbering plan interworking and/or address signalling methods for: .LP \(em calls originated in an ISDN for terminals on another ISDN, or terminals on a dedicated network, and .LP \(em calls originated in a PSTN for terminals on an ISDN. .PP This Recommendation complements other CCITT Recommendations (e.g.,\ Recommendation\ X.122) which focus on numbering plan interworking for calls originated from terminals on dedicated networks (other than PSTN) and which are intended for compatible terminals on an ISDN. .PP 2.5 For the purposes of this Recommendation, ISDNs can, where appropriate, be assumed to provide both ISDN and PSTN access. In this case, the originating ISDN will generally be unable to differentiate between the two types of access in the terminating network based on the called\ E.164 number. .PP It is the responsibility of the terminating network to establish appropriate bilateral arrangements to ensure successful interworking to serve both its ISDN and PSTN customers. .sp 2P .LP \fB3\fR \fBInterworking arrangements\fR .sp 1P .RT .PP 3.1 To allow an ISDN subscriber to set up calls intended for completion on other networks, the following two basic methods are available: .sp 9p .RT .sp 1P .LP 3.1.1 \fISingle stage method\fR .sp 9p .RT .PP Interworking by using single stage dialling (or equivalent) is achieved by an arrangement where the calling party accesses a different type of network by selecting a numbering plan indicator, e.g.,\ NPI ( numbering plan identifier in Recommendation\ Q.931) or an escape code consisting of one or more digits (see Recommendation\ E.160 for definition of escape code), which determines the type of destination network (i.e.,\ its numbering plan). The NPI and/or escape code is then followed by the address of the called terminal on the destination network. The originating network provides the necessary intelligence to route the call to the appropriate interworking function (IWF), to ensure delivery of the call to the destination network. .RT .sp 1P .LP 3.1.2 \fITwo\(hystage method\fR .sp 9p .RT .PP The two\(hystage selection method of interworking is an arrangement wherein the first stage of selection establishes a connection from the calling subscriber's terminal to an IWF associated with a point\(hyof\(hypresence of, or gateway to, the desired destination network or an appropriate transit network. To gain access to the IWF, the calling subscriber uses selection procedures assigned to the IWF within the originating network, i.e.,\ the IWF is assigned a number from the numbering plan of the originating network. .PP When the first connection has been established, the IWF sends a response to the calling terminal. Upon receipt of this response, the calling subscriber is required to input, as a second stage of selection, the address information of the called terminal in the destination network. This second called address information is passed transparently through the originating network and the IWF to the receiving equipment on the destination network. Having received the second address, conforming to the numbering plan of the destination network, the destination network will establish a connection from the IWF to the called terminal, thus completing the connection from the originating terminal to the destination terminal. .RT .PP 3.2 The choice of the numbering plan interworking arrangement should ensure that the impact on the user is minimized and there is no requirement for complex selection procedures. Single\(hystage methods are therefore recommended for numbering plan interworking between ISDN and dedicated networks. Solutions adopted to achieve this interworking arrangement for short\(hyterm and long\(hyterm applications are covered in subsequent sections. The short\(hyterm and long\(hyterm are time frames related to Time\ \fIT\fR as specified in Recommendation\ E.165. .PP 3.3 Special situations in which two\(hystage interworking arrangements may apply and corresponding partitioning of responsibilities between originating, transit and destination networks are for further study. .PP 3.4 It is recognized that some Administrations may not be able to offer interworking capability for international traffic. Bilateral arrangements may therefore be required to provide interworking capability. Because of administrative difficulties, interworking should not be performed across the international boundary, unless no other interworking possibilities exist. .bp .PP 3.5 Some networks may select other interworking arrangements, such as operator assistance, to complete the call. The need to standardize such interworking arrangements is for further study. .sp 2P .LP \fB4\fR \fBInterworking evolution\fR .sp 1P .RT .PP 4.1 The recommended long\(hyterm numbering plan interworking solution is based on the NPI/TON field in the ISDN call set\(hyup message as defined in Recommendation\ Q.931. The NPI element is the numbering plan identifier (e.g.,\ Recommendation\ E.164/E.163, X.121, F.69), whereas the TON indicates the type of number (e.g.,\ local, national, international). This NPI/TON field will be carried as part of the call set\(hyup message to the originating exchange, which will use this information to route the call. The NPI element will also be available within the network as part of the address message in S.S. No.\ 7 ISUP. .sp 9p .RT .PP 4.2 The network capabilities in terms of digit storage, digit analysis and signalling protocols to implement the NPI\(hybased interworking solutions on a global basis will not be available in the short term. Thus, a single\(hystage method for numbering plan interworking in the short term, and a timetable for planned evolution to the NPI/TON\(hybased, long\(hyterm solution have been proposed (see Recommendation\ E.165). .PP 4.3 The short\(hyterm, single\(hystage interworking arrangements will use prefixes and escape codes to indicate the type of number and numbering plan of the destination network, respectively. Definitions of prefixes and escape codes are contained in Recommendation\ E.160. As indicated in Recommendation\ E.160, prefixes are not part of the number and are not signalled over internetwork or international boundaries so that they are not subject to international standards. Escape codes, however, may be carried forward through the originating network and across internetwork and international boundaries. Therefore, the values of escape codes need to be standardized. .PP Table A\(hy1/E.166 summarizes the escape codes recommended by CCITT for numbering plan interworking. Note that escape codes for interworking between ISDNs and PSTNs are not required because the PSTN numbering plan (Recommendation\ E.163) is a subset of the numbering plan for the ISDN era. (Recommendation\ E.164). .PP There may be cases when a standardized escape code is numerically equal to a prefix already in use in the network. In such cases, an optional network\(hyspecific digit(s) other than the standardized escape code may be used, and the translation from the optional\(hynetwork\(hyspecific digit(s) to the standardized escape code is performed by the network. .PP To facilitate short\(hyterm interworking (using escape codes) between ISDNs and existing dedicated networks, Recommendation\ E.165 specifies that the international numbers assigned to ISDN user\(hynetwork interfaces will be restricted to a maximum of twelve digits till Time \fIT\fR . Time \fIT\fR is specified in Recommendation\ E.165. After time\ \fIT\fR , ISDNs can implement the full capability of the ISDN numbering plan (Recommendation\ E.164). Recommendation\ E.165, and the date specified for time\ \fIT\fR , provide guidelines for evolution towards full ISDN numbering and numbering plan interworking capabilities. .RT .PP 4.4 The numbering plan interworking solutions in this Recommendation are categorized as short\(hyterm (pre\(hy Time\ \fIT\fR , using escape codes) and long\(hyterm (post\(hy Time\ \fIT\fR , using NPI/TON). It is however envisaged that, based on their individual network evolution plans, some Administrations will implement the NPI/TON\(hybased inter working solutions prior to Time\ \fIT\fR . Introduction of NPI/TON\(hybased interworking in a given network prior to Time\ \fIT\fR should not impose any specific requirements on networks not supporting NPI/TON for interworking, unless bilaterally agreed. .PP 4.5 The man\(hymachine interface procedures used with ISDN terminals to indicate the appropriate NPI and TON are for further study. .sp 2P .LP \fB5\fR \fBRepresentative interworking scenarios\fR .sp 1P .RT .PP 5.1 This section provides single\(hystage interworking solutions for a number of representative interworking scenarios. The scenarios presented are not exhaustive. .sp 9p .RT .PP 5.2 It is assumed that all ISDNs and ISDN terminals will support the NPI/TON feature from their inception and that a NPI/TON equivalent feature will be available in PDNs by Time\ \fIT\fR , if not earlier. .bp .PP 5.3 The interworking scenarios presented in this section assume that the called and calling numbers represent international number formats in the appropriate numbering plans. Partitioning of the international number for local and national calls and the associated prefixes are a national matter and are not indicated in the interworking solutions. .PP 5.4 The interworking cases addressed in Figures 2/E.166 to 11/E.166 are indicated by the boxes with numbers in the matrix of Table\ 1/E.166, where the numbers in the boxes refer to the appropriate Figures (2/E.166 to\ 11/E.166). Other numbering plan interworking scenarios are for further study. .ce \fBH.T. [T1.166]\fR .ce TABLE\ 1/E.166 .ce \fBMatrix of interworking cases and the figures in which .ce they are shown\fR .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(42p) | cw(36p) | cw(30p) sw(30p) sw(30p) sw(30p) sw(30p) , ^ | ^ | c | c | c | c | c. Networks Terminals ISDN ISDN V Series Rec. X.25 Rec. X.21 Telex _ .T& lw(42p) | lw(36p) | cw(30p) | lw(30p) | lw(30p) | cw(30p) | lw(30p) , ^ | l | l | l | l | l | l ^ | l | l | l | l | l | l ^ | l | l | l | l | l | l ^ | l | l | l | l | l | l. ISDN ISDN 2 V Series Rec. X.25 6, 10 Rec. X.21 Telex _ .T& lw(42p) | lw(36p) | cw(30p) | lw(30p) | cw(30p) | lw(30p) | cw(30p) , ^ | l | l | l | l | l | l ^ | l | l | l | l | l | l ^ | l | l | l | l | l | l ^ | l | l | l | l | l | l. PSTN Voice 3 V Series 4 Rec. X.25 5 _ .T& lw(42p) | lw(36p) | cw(30p) | lw(30p) | cw(30p) | lw(30p) | cw(30p) , ^ | l | l | l | l | l | l ^ | l | l | l | l | l | l ^ | l | l | l | l | l | l ^ | l | l | l | l | l | l. PSPDN Rec. X.25 7, 11 _ .T& lw(42p) | lw(36p) | cw(30p) | lw(30p) | cw(30p) | lw(30p) | cw(30p) , ^ | l | l | l | l | l | l ^ | l | l | l | l | l | l ^ | l | l | l | l | l | l ^ | l | l | l | l | l | l. CSPDN Rec. X.21 8 _ .T& lw(42p) | lw(36p) | cw(30p) | lw(30p) | cw(30p) | lw(30p) | cw(30p) , ^ | l | l | l | l | l | l ^ | l | l | l | l | l | l ^ | l | l | l | l | l | l ^ | l | l | l | l | l | l. Telex Telex 9 _ .TE .nr PS 9 .RT .ad r \fBTable 1/E.166 [T1.166], p.\fR .sp 1P .RT .ad b .RT .PP 5.5 The following abbreviations are used in Figures 2/E.166 to 11/E.166 which contain short\(hyterm and long\(hyterm interworking solutions for representative configurations: .LP Cd Called number .LP Cg Calling number .LP IWF Interworking function .LP PH Packet handler .LP M Modem .LP NPI/TON Numbering plan identifier/Type of number feature as defined in Recommendation\ Q.931 .LP CRP Call request packet in Recommendation X.25 .LP TA Terminal adapter .PP \fINote\fR \ \(em\ As stated in Recommendation X.25, presence of the calling number, i.e., address (Cg) in the call request packet (CRP) is not mandatory. However, even when it is given by the calling terminal, this does not preclude the network from checking and possibly modifying this information, e.g.,\ for security reasons. .PP 5.6 Interworking solutions in the reverse direction, i.e., dedicated networks to ISDN, are also indicated in Figures\ 2/E.166 to 11/E.166. However, except for PSTN to ISDN calls, these may also be the subject of complementary CCITT Recommendations (e.g.,\ Recommendation\ X.122). .bp .LP .rs .sp 22P .ad r \fBFigure 2/E.166, p.10\fR .sp 1P .RT .ad b .RT .LP .rs .sp 25P .ad r \fBFigure 3/E.166, p.11\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 23P .ad r \fBFigure 4/E.166, p.12\fR .sp 1P .RT .ad b .RT .LP .rs .sp 26P .ad r \fBFigure 5/E.166, p.13\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 23P .ad r \fBFigure 6/E.166, p.14\fR .sp 1P .RT .ad b .RT .LP .rs .sp 26P .ad r \fBFigure 7/E.166, p.15\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 25P .ad r \fBFigure 8/E.166, p.16\fR .sp 1P .RT .ad b .RT .LP .rs .sp 23P .ad r \fBFigure 9/E.166, p.17\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 21P .ad r \fBFigure 10/E.166, p.18\fR .sp 1P .RT .ad b .RT .LP .rs .sp 20P .ad r \fBFigure 11/E.166, p.\fR .sp 1P .RT .ad b .RT .PP 5.7 The location of the IWF and PH symbols in the diagrams does not imply a fixed position in the network or place any limitations on their functionalities. .bp .ce 1000 ANNEX\ A .ce 0 .ce 1000 (to Recommendation E.166) .sp 9p .RT .ce 0 .ce 1000 \fBEscape codes for numbering plan interworking\fR .sp 1P .RT .ce 0 .PP Table A\(hy1/E.166 summarizes the escape codes that are recommended for interworking between different CCITT\(hydefined numbering plans referred to in this Recommendation. .sp 1P .RT .ce \fBH.T. [T2.166]\fR .ce TABLE\ A\(hy1/E.166 .ce \fBRecommended escape codes for numbering plan interworking\fR .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(54p) | cw(54p) | cw(54p) | cw(66p) . From To Escape code Remarks _ .T& lw(54p) | lw(54p) | cw(54p) | lw(66p) . ISDN (Rec. E.164) PSPDN (Rec. X.121) `0' Note 1 _ .T& lw(54p) | lw(54p) | cw(54p) | lw(66p) . ISDN (Rec. E.164) CSPDN (Rec. X.121) \(em { Need for an escape code is for further study } _ .T& lw(54p) | lw(54p) | cw(54p) | lw(66p) . PDN (Rec. X.121) ISDN (Rec. E.164) `0' Note 2 _ .T& lw(54p) | lw(54p) | cw(54p) | lw(66p) . Telex (Rec. F.69) ISDN (Rec. E.164) \(em { Need for an escape code is for further study } .TE .LP \fINote\ 1\fR \ \(em\ Use of escape code digit `0' for ISDN to PSPDN numbering plan interworking is restricted to packet data calls originated from an X.25 DTE on an ISDN using an X.31 TA and are a short\(hyterm (up to time \fIT\fR defined in Recommendation\ E.165) measure. .LP \fINote\ 2\fR \ \(em\ Under certain implementation, escape code digit `9' may also be used (see Recommendation\ X.121). .nr PS 9 .RT .ad r \fBTableau A\(hy1/E.166 [T2.166], p.20\fR .sp 1P .RT .ad b .RT .LP .rs .sp 15P .ad r BLANC .ad b .RT .LP .bp .ce 1000 ANNEX\ B .ce 0 .ce 1000 (to Recommendation E.166) .sp 9p .RT .ce 0 .ce 1000 \fBAdditional short\(hyterm numbering plan interworking scenarios\fR .sp 1P .RT .ce 0 .ce 1000 \fBfor \fBpacket\(hydata services\fR .ce 0 .PP The following scenarios may be used in special circumstances in the short term: .sp 1P .RT .LP .rs .sp 40P .ad r \fBFigure B\(hy1/E.166, p.21\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 22P .ad r \fBFigure B\(hy2/E.166, p.22\fR .sp 1P .RT .ad b .RT .sp 2P .LP \fBRecommendation\ E.167\fR .RT .sp 2P .sp 1P .ce 1000 \fBISDN\ NETWORK\ IDENTIFICATION\ CODES\fR .EF '% Fascicle\ II.2\ \(em\ Rec.\ E.167'' .OF '''Fascicle\ II.2\ \(em\ Rec.\ E.167 %' .ce 0 .sp 1P .LP \fB1\fR \fBGeneral\fR .sp 1P .RT .PP This Recommendation presents the interim structure for the ISDN Network Identification Code (INIC) that is used to identify an ISDN network in Closed User Group (CUGs) and in certain\ X.75 utilities. The interim INIC does not form any part of an\ E.164 number. .PP The structure of a permanent INIC has not been agreed, and is for urgent further study. .RT .sp 2P .LP \fB2\fR \fBUsage\fR .sp 1P .RT .sp 1P .LP 2.1 \fIClosed user groups\fR .sp 9p .RT .PP The format of the Interlock Code (IC) in Signalling System No.\ 7 is based on the format defined in Recommendation\ X.180 concerning closed user group utilities and used in Recommendation\ X.75, i.\ e., a 32\ bit code divided into two parts. Part\ A is 16\ bits and is coded to identify a 4\ digit number, and Part\ B is coded as a 16\ bit equivalent of a decimal number. .PP \fR Part A will consist of an interim INIC [or a Data Network Identification Code (DNIC)] to identify the individual ISDN (or PDN) that is responsible for administering the closed user group (CUG). Part\ A of the IC contains space for a string of 4 decimal digits. The interim INIC thus is a string of 4 digits beginning with a digit that distinguishes interim INICs from any DNIC. .RT .sp 1P .LP 2.2 \fIX.75\fR \fIutilities\fR .sp 9p .RT .PP The interim INIC can be used to identify an ISDN in the TNIC (Transit Network Identification Code) and CNIC (Clearing Network Identification Code) CUG utilities of the X.75 protocol. .bp .RT .sp 2P .LP \fB3\fR \fBFormat of the\fR \fBinterim ISDN network identification code\fR .sp 1P .RT .sp 1P .LP 3.1 \fIDefinition\fR .sp 9p .RT .PP The \fBinterim INIC\fR is a string of 4 digits. Each different string of digits may be used to identify an individual ISDN. The first digit\ I distinguishes the INIC from a DNIC. This digit is followed by the country code from the E.163/E.164 numbering plan which has a length of one, two or three digits (see Recommendation\ E.163). The E.163/E.164 country code is followed by enough additional digits, X, to make the total length of the INIC 4\ digits. The format is shown in Table\ 1/E.167. .RT .ce \fBH.T. [T1.167]\fR .ce TABLE\ 1/E.167 .ce \fBFormat of the interim INIC\fR .ce I is the initial digit, C is a digit of the country code .ce and X is an additional digit .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(72p) | cw(60p) . Country code INIC Format _ .T& cw(72p) | cw(60p) . One digit ICXX _ .T& cw(72p) | cw(60p) . Two digits ICCX _ .T& cw(72p) | cw(60p) . Three digits ICCC _ .TE .nr PS 9 .RT .ad r \fBTable 1/E.167 [T1.167], p.\fR .sp 1P .RT .ad b .RT .sp 1P .LP 3.2 \fIDigit I\fR .sp 9p .RT .PP The digit I may be 0 or 9. The use of the digits 8 and 1 as the digit I requires further study. .RT .sp 1P .LP 3.3 \fIAdditional digits\fR .sp 9p .RT .PP Each additional digit is a digit in the range 0 to 9. .RT .sp 1P .LP 3.4 \fIOther formats\fR .sp 9p .RT .PP The formats 00XX and 90XX could provide for 200 additional INICs not associated with specific country codes. These are for further study. .RT .sp 1P .LP 3.5 \fIAdministration\fR .sp 9p .RT .PP Each unique combination of digit\ I, country code, and additional digit(s) can identify a different ISDN, or part of an ISDN. .PP The Administration to which the country code has been assigned is responsible for administering the digit\ I and the additional digit(s). .PP Within each country, it is suggested that the INICs beginning with the digit I\ =\ 0 be assigned first, followed by INICs beginning with the digit I\ =\ 9. .RT .sp 1P .LP 3.6 \fIDuration of the interim definition\fR .sp 9p .RT .PP The interim INIC is for immediate use. Its use will continue until a permanent definition has been agreed to, and a period beyond that to allow a transition to the use of the permanent definition. .RT .sp 2P .LP \fB4\fR \fBFurther usage\fR .sp 1P .RT .PP While other uses of the interim INIC are possible, proponents of such use are strongly urged to consider that their implementation should be easily adaptable to the permanent format of the INIC. .RT .sp 2P .LP \fB5\fR \fBFormat of the permanent ISDN network identification code\fR .sp 1P .RT .PP The definition of the permanent format of the INIC is for urgent further study. .RT .LP .bp .LP \fBMONTAGE:\ \fR PAGE 156 = PAGE BLANCHE .sp 1P .RT .LP .bp