Suggestions how to manage telephony numberplan
Hi there,
are there among you perhaps people who have something like this implemented already or have suggestions how to do it?
Basically I consider to build an app to replace a spreadsheet that will become in the end unmanageable and also make the data better sharable with others.
It's all around telephony number-plans.
In principle the Telecom Provider will provides a range of numbers (by 1's, by 10's, by 100's, by 1000's etc)
For example the provider assigns number range 010 2222 36xx which is basically a range of 100 numbers first one is 010 2222 3600 and the last one is 010 2222 3699.
------------------------------
Jan-Willem S
------------------------------
are there among you perhaps people who have something like this implemented already or have suggestions how to do it?
Basically I consider to build an app to replace a spreadsheet that will become in the end unmanageable and also make the data better sharable with others.
It's all around telephony number-plans.
In principle the Telecom Provider will provides a range of numbers (by 1's, by 10's, by 100's, by 1000's etc)
For example the provider assigns number range 010 2222 36xx which is basically a range of 100 numbers first one is 010 2222 3600 and the last one is 010 2222 3699.
We can make it more complicated and it is more complicated as 010 2222 3[67]xx could also be assigned as 2 blocks of 100. Starting at ...3600 en ending at ...6799. And if that is not enough complicated it could also be 010 2222 3[679]xx (note the 8 is missing) which would stand for 3 blocks of 100 starting at ...3600 en pausing at ...3799 and than continuing on ...3900 and ending at ...3999.
But let's skip these complications for now.
Potentially I'm looking at thousands of number-plans with hundreds of telephone numbers in each number-plan.
My primary thoughts were to create two tables.
One to keep track of the parent-ranges in use with details like the provider, the circuit, the handover details etc etc.
And second a child-table with all the individual telephone numbers that fit in the parent-range and their specific details like who is the user, what specific function is it used for, where is it located, etc etc.
My main challenge at this moment is how to create preferable automatically all those individual telephone numbers in the child table once the 'parent-range' is created???
Thanks
Jan-Willem
PS.
1
I've been looking at an earlier and was wondering if this is possible start.
https://community.quickbase.com/communities/community-home/digestviewer/viewthread?GroupId=103&MessageKey=8d321e15-bd9a-4f49-b4c9-e89822b6677f&CommunityKey=d860b0f8-6a48-487b-b346-44c47a19a804&tab=digestviewer
2
To workaround the multiple and broken ranges complication as described above I tend to solve this by simply creating multiple unbroken parent-ranges in the parent-table and most probably join them via a internal link: parent-table --> parent-table
3
Once this is solved my next logical step is something similar for IP-subnets and IP-numbers
But let's skip these complications for now.
Potentially I'm looking at thousands of number-plans with hundreds of telephone numbers in each number-plan.
My primary thoughts were to create two tables.
One to keep track of the parent-ranges in use with details like the provider, the circuit, the handover details etc etc.
And second a child-table with all the individual telephone numbers that fit in the parent-range and their specific details like who is the user, what specific function is it used for, where is it located, etc etc.
My main challenge at this moment is how to create preferable automatically all those individual telephone numbers in the child table once the 'parent-range' is created???
Thanks
Jan-Willem
PS.
1
I've been looking at an earlier and was wondering if this is possible start.
https://community.quickbase.com/communities/community-home/digestviewer/viewthread?GroupId=103&MessageKey=8d321e15-bd9a-4f49-b4c9-e89822b6677f&CommunityKey=d860b0f8-6a48-487b-b346-44c47a19a804&tab=digestviewer
2
To workaround the multiple and broken ranges complication as described above I tend to solve this by simply creating multiple unbroken parent-ranges in the parent-table and most probably join them via a internal link: parent-table --> parent-table
3
Once this is solved my next logical step is something similar for IP-subnets and IP-numbers
------------------------------
Jan-Willem S
------------------------------
