Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Range of 6 numbers
- Thread starter aau2
- Start date
Have you tried stating the first of the 6 digits as common abbreviated dialling?
For example, Let´s say that you want extension range to be 150000 to 159999
NANSI:NUMTYP=EX,NUMSE=50000&&59999;
NANSI:NUMTYP=AC,NUMSE=15;
ADCOI:ABB=15,TRA=5,CLASS=0&&3;
Hope it helps.
Rodrigo.
For example, Let´s say that you want extension range to be 150000 to 159999
NANSI:NUMTYP=EX,NUMSE=50000&&59999;
NANSI:NUMTYP=AC,NUMSE=15;
ADCOI:ABB=15,TRA=5,CLASS=0&&3;
Hope it helps.
Rodrigo.
- Thread starter
- #5
HI all
It is patches bases and does not need any recompiled PU.
The purpose is to add a digit in front of an extension number in idle state as well as for call ringing state and call established state.
The added digit is entered in the system in a SACOS line.
Supported interfaces
-Analogue extensions
-Digital extensions
-IP extensions.
-Operators
-Voice Mail
-SMDR
Not supported or remaining as 5 digit entities
-All MML command handling, including procedure execution via command
-ACD, ANCD, CCM and CCA
-Data extensions and ISDN S0 extensions
-DECT SMS.
-Paging.
-Message Diversion (positions and IC protocol)
-Electronic Mail (EM) protocol
-MIS (for ACD)
-ApplicationLink
As the idea is to have only a presentation based on 6 digits, all dialling (incoming external call as well as internal calls) must be translated into a 5 digits numbering plan.
this is achieve by NUTRI and Inbound conversion.
Example : 10000 series and 30000 series are supposed to be extension/OP/IP/GH...
6 is supposed to be the leading digit; this digit is entered as SACOS line
Now when an Extension dial internally, you you do NUTRY:ENTRY=61,CNVTYP=4,TRC=1; and
NUTRY:ENTRY=63,CNVTYP=4,TRC=1;
In that case Extension 611111 calling 631111, mean in reallity a call between 11111 and 31111.
In that case, extension can still call each other internally by their own 5 digits numbers !
To avoid this, you should do an other NUTRI with CNVTYP=4 to analyse 10000 and 30000 series to avoid calls or redirect that dialling to the correct party.
Incoming external call should have a NUTRI (of course if necessary) to reach a correct number.
I don't have tested DECT as the customer don't have it.
Freesseting and Mobile extension works.
Best regards
It is patches bases and does not need any recompiled PU.
The purpose is to add a digit in front of an extension number in idle state as well as for call ringing state and call established state.
The added digit is entered in the system in a SACOS line.
Supported interfaces
-Analogue extensions
-Digital extensions
-IP extensions.
-Operators
-Voice Mail
-SMDR
Not supported or remaining as 5 digit entities
-All MML command handling, including procedure execution via command
-ACD, ANCD, CCM and CCA
-Data extensions and ISDN S0 extensions
-DECT SMS.
-Paging.
-Message Diversion (positions and IC protocol)
-Electronic Mail (EM) protocol
-MIS (for ACD)
-ApplicationLink
As the idea is to have only a presentation based on 6 digits, all dialling (incoming external call as well as internal calls) must be translated into a 5 digits numbering plan.
this is achieve by NUTRI and Inbound conversion.
Example : 10000 series and 30000 series are supposed to be extension/OP/IP/GH...
6 is supposed to be the leading digit; this digit is entered as SACOS line
Now when an Extension dial internally, you you do NUTRY:ENTRY=61,CNVTYP=4,TRC=1; and
NUTRY:ENTRY=63,CNVTYP=4,TRC=1;
In that case Extension 611111 calling 631111, mean in reallity a call between 11111 and 31111.
In that case, extension can still call each other internally by their own 5 digits numbers !
To avoid this, you should do an other NUTRI with CNVTYP=4 to analyse 10000 and 30000 series to avoid calls or redirect that dialling to the correct party.
Incoming external call should have a NUTRI (of course if necessary) to reach a correct number.
I don't have tested DECT as the customer don't have it.
Freesseting and Mobile extension works.
Best regards
- Thread starter
- #7
- Thread starter
- #9
Hi
There is only a generic name for this feature which is call "6 digits Numbering plan" and you should request that feature.
Now the patch number are 107913/107914/107915/107916/108379/110751/110752
So far the patches have been tested on BC12 SP9 and CFREI is right : if you have OneBox and DNA integration, you must choose if you will have a OB system with 6 digits or 5 digits as DNA is not able to handle 6 digits numbering plan....
There is only a generic name for this feature which is call "6 digits Numbering plan" and you should request that feature.
Now the patch number are 107913/107914/107915/107916/108379/110751/110752
So far the patches have been tested on BC12 SP9 and CFREI is right : if you have OneBox and DNA integration, you must choose if you will have a OB system with 6 digits or 5 digits as DNA is not able to handle 6 digits numbering plan....
- Thread starter
- #12
Hi
Take a look a this section of my previous post
Not supported or remaining as 5 digit entities
-All MML command handling, including procedure execution via command
-ACD, ANCD, CCM and CCA
-Data extensions and ISDN S0 extensions
-DECT SMS.
-Paging.
-Message Diversion (positions and IC protocol)
-Electronic Mail (EM) protocol
-MIS (for ACD)
-ApplicationLink
Take a look a this section of my previous post
Not supported or remaining as 5 digit entities
-All MML command handling, including procedure execution via command
-ACD, ANCD, CCM and CCA
-Data extensions and ISDN S0 extensions
-DECT SMS.
-Paging.
-Message Diversion (positions and IC protocol)
-Electronic Mail (EM) protocol
-MIS (for ACD)
-ApplicationLink
- Thread starter
- #14
- Status