10-03-2013 12:02 AM - edited 03-16-2019 07:40 PM
Originally posted: 2013-Oct-03.
More than two years ago, I informed Cisco that various pieces of documentation detailing the GB number plan were inaccurate, incomplete, and out of date.
The majority of the published data seemed to be from some time back between 2003 and 2006, but with a substantial number of additional errors and inaccuracies and certainly not up to date.
It took the best part of a year to get the documentation amended and then more than a year for the software to be updated, viz.: dp-ffr.3-1-30.GB.cop.sgn
The new file can be found at:
Visit the above page, mouseover the details there, then look for the 'flat pattern file' link in the popup box, specifically:
http://www.cisco.com/web/software/282074292/105507/GBNP.txt
For the first time in more than a decade, the GB number plan functions correctly.
There are several (mostly minor) issues remaining and these will be detailed in several posts following this one.
The files below also track the changes (except for item 4).
10-03-2013 12:09 AM
Item 1
# VERSION : 29
The file is version 30 but incorrectly identifies as version 29.
# VERSION : 30
10-03-2013 12:10 AM
Item 2
The pattern for 03 numbers allows any 10-digit NSN beginning 03 (the leading zero does not count towards the NSN).
# 0+3XXXXXXXXX
P: 0 NATIONAL-ACCESS
P: 3XXXXXXXXX 03-NUMBER
T: N
C: LONGDISTANCE
E: +,[COUNTRY-CODE],03-NUMBER
F: NATIONAL-ACCESS,03-NUMBER
S: Y
In reality, only those beginning 030, 033, 034 and 037 are likely to be issued any time soon.
# 0+3[0347]XXXXXXXX
P: 0 NATIONAL-ACCESS
P: 3[0347]XXXXXXXX 03-NUMBER
T: N
C: LONGDISTANCE
E: +,[COUNTRY-CODE],03-NUMBER
F: NATIONAL-ACCESS,03-NUMBER
S: Y
Ranges already in use: 0300, 0302, 0303, 0306, 0330, 0331, 0332, 0333.
Ranges already in use: 0343, 0344, 0345, 0370, 0371, 0372.
Ranges coming into use soon: 0342, 0373, maybe others beginning 030x or 033x.
If other 03x ranges come into use, there will likely be several years warning.
10-03-2013 12:13 AM
Item 3
# 0+870+XXXXXXX
P: 0 NATIONAL-ACCESS
P: 870 LOCALRATE-ACCESS
P: XXXXXXX LOCALRATE-SUBSCRIBER
T: N
C: LONGDISTANCE
E: +,[COUNTRY-CODE],LOCALRATE-ACCESS,LOCALRATE-SUBSCRIBER
F: NATIONAL-ACCESS,LOCALRATE-ACCESS,LOCALRATE-SUBSCRIBER
S: Y
# 0+87[1-3]+XXXXXXX
P: 0 NATIONAL-ACCESS
P: 87[1-3] NATIONALRATE-ACCESS
P: XXXXXXX NATIONALRATE-SUBSCRIBER
T: N
C: LONGDISTANCE
E: +,[COUNTRY-CODE],NATIONALRATE-ACCESS,NATIONALRATE-SUBSCRIBER
F: NATIONAL-ACCESS,NATIONALRATE-ACCESS,NATIONALRATE-SUBSCRIBER
S: Y
Ofcom are currently in a lengthy process of "simplifying non-geographic numbers", with likely implementation early in 2015.
0870 numbers have not been aligned with geographic pricing since 2004. Since 2009 revenue share has also been removed.
However, under the new plans 0870 is likely to return to revenue sharing and be equivalent to the 0871, 0872, 0873 range.
# 0+87[0-3]+XXXXXXX
P: 0 NATIONAL-ACCESS
P: 87[0-3] NATIONALRATE-ACCESS
P: XXXXXXX NATIONALRATE-SUBSCRIBER
T: N
C: LONGDISTANCE
E: +,[COUNTRY-CODE],NATIONALRATE-ACCESS,NATIONALRATE-SUBSCRIBER
F: NATIONAL-ACCESS,NATIONALRATE-ACCESS,NATIONALRATE-SUBSCRIBER
S: Y
10-03-2013 07:45 AM
10-03-2013 12:26 AM
Item 4
Some of the names for the types of numbers are misleading.
LOCALRATE-ACCESS
LOCALRATE-SUBSCRIBER
NATIONALRATE-ACCESS
NATIONALRATE-SUBSCRIBER
0845 numbers were aligned to local-rate pricing, but only from certain landlines, and only until 2004.
0870 numbers were aligned to national-rate pricing, but only from certain landlines, and only until 2004.
Other 084 and 087 numbers have never been aligned with geographic-rate pricing in any way whatsoever.
Ofcom's "simplifying non-geographic numbers" project will end up with 084 and 087 numbers being classed as revenue share numbers with an Access Charge and a Service Charge to be declared by the respective parties, and a requirement that all refererences to "local" or "national" rates be removed.
090x and 091x numbers are Premium Rate Services (PRS), and 098x numbers are S**ual/Adult Entertainment Services (SES), both using NTS (Number Translation Services).
08xx numbers are also NTS, and I would suggest the following names:
NTS084-ACCESS
NTS084-SUBSCRIBER
NTS087-ACCESS
NTS087-SUBSCRIBER
Ofcom currently refer to them as "08 numbers", but that causes confusion because "08 numbers" isn't supposed to include 080 numbers, which clearly also begin with 08!
Whatever you decide, the terms "local" and "national" should go as they haven't applied for nearly a decade.
10-03-2013 12:31 AM
Item 5
The following number ranges were removed from the GB Number Plan many years ago.
# 0+9[2-79]XXXXXXXX
P: 0 NATIONAL-ACCESS
P: 9[2-79]XXXXXXXX BROADBAND-SERVICE
T: N
C: LONGDISTANCE
E: +,[COUNTRY-CODE],BROADBAND-SERVICE
F: NATIONAL-ACCESS,BROADBAND-SERVICE
S: Y
It may be that you're leaving them in because removing could create instability in existing installations.
Previously, this pattern also matched 098 numbers and people could potentially use it to allow access to adult chat lines. That loophole has been closed by matching only 9[2-79]XXXXXXXX numbers now. All numbers matched by this new version of the rule are currently unallocated in the UK.
10-03-2013 12:32 AM
Item 6
There are some extraneous TABs and trailing spaces in the file.
Run both 'convert tabs to spaces' and 'trim trailing spaces' in a text editor.
This is cosmetic only and has absolutely no bearing on functionality.
10-14-2013 05:56 PM
10-03-2013 12:34 AM
Item 7
The heading is incorrect.
# Services, Mobile & Non Geographic Calls
Below that heading only one type of number is found.
# Services
10-03-2013 12:36 AM
Item 8
The arrangement of the various items is completely disorganised.
This makes it much more difficult to check for errors and makes it easy for new errors to be introduced.
Rules that cover similar number types should be adjacent.
Move # 0+13873+[2-9]XXXX to be before # 0+15242+[2-9]XXXX.
Move # 0+1768[347]+[2-9]XXXX to be before # 0+19467+[2-9]XXXX.
Move # 0+1827+[56]XXXX into numerical order further down the page, just before # 0+1837+5[2-5]XXX.
Move # 0+1524+3[2-79]XXX and # 0+1524+6XXXX into numerical order much further down the page.
Move # 0+16977+[23]XXX to be just after # 0+19467+[2-9]XXXX.
Move # 0+1768+88[234678]XX to be before # 0+1827+[56]XXXX and # 0+1837+5[2-5]XXX.
Swap the order of # 0+1750+[3-68]2XXX and # 0+1750+2[0-3]XXX.
Move # 0+56XXXXXXXX to be near # 0+55XXXXXXXX.
Put in numerical order: # 0+55XXXXXXXX, # 0+56XXXXXXXX, # 0+70+XXXXXXXX and # 0+76+XXXXXXXX.
Move # 112 and # 999 to be at the end, last in the file.
10-03-2013 12:40 AM
Item 9
The section headings are disorganised and do not match the content that follows them:
# Long Distance Calls
# International Calls
# Services, Mobile & Non Geographic Calls
Suggest a new approach:
# Local Calls
(4, 5, 6, 7 and 8 digit local numbers)
# Long Distance Calls - 10 digits
(011x, 01x1, 01xxx, 01xxxx, 02x)
# Long Distance Calls - 9 digits
(01xxx various prefixes, 016977)
# Non-geographic Numbers Charged at Geographic Rates
(030, 033, 034, 037)
# VoIP, Corporate, Personal and Pager Numbers
(055, 056, 070, 076)
# Mobile Numbers
(071-075, 07624, 077-079)
# Non-geographic Numbers - 10 digits
(080, 084, 087, 082)
# Non-geographic Numbers - 9 digits
(0500, 0800)
# Non-geographic Numbers - 7 digits
(0800 1111, 0845 4647)
# Premium Rate Numbers
(090, 091, 098)
# International Calls
(00 prefix)
# Services
(1xx, 116xxx, 118xxx, 1xxx, 18xxx)
# Emergency
(112, 999)
Number plan maintenance will become much easier if there is some sort of logic and organisation to the data.
10-03-2013 12:45 AM
The page at
should link to the README file at
http://www.cisco.com/web/software/282074292/105507/dp-ffr-3-1-30_GBNP_Readme.txt
but the link is missing.
The same error was made when 3.1.29 was released.
Section 1 of the README mentions CSCuc48084 and links to a post within
https://supportforums.cisco.com/thread/2171992.
It should now also mention CSCug82402 and CSCuh62857 and link to
https://supportforums.cisco.com/thread/2214042
as that thread contains the details of what version 3.1.30 fixes.
The README links to
for software download. That's version 3.1.4 for ITALY not version 3.1.30 for the UK.
The same error was made when 3.1.28 and 3.1.29 were released.
The README file links to
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/idp/504_423/deploy/dpdg.html
but that documentation (especially the GBNP dialplan details at
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/idp/504_423/deploy/dpDlPlns.html#wp1042320
) is full of errors.
The newer version, with less errors, is here
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/idp/911/deploy/dpDlPlns.html#wp1042716
It was corrected more than a year ago.
The same error was made when 3.1.28 and 3.1.29 were released.
In section 4 of the README, defect CSCuc48084 should also be mentioned in the list.
Cisco's legendary lack of attention to detail continues.
10-03-2013 01:42 AM
There doesn't appear to be any matching 1.1.x or 2.1.x versions published here:
Are those products no longer supported or is this an oversight?
Anyone else found anything that I have missed?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide