How to block an incoming call?

[BrianQHong]

Anyone know how to block selected incoming calls from the MD110? I know how to block calls using script manager, but don't know much about MD110.

 

[alchohaz]

Incoming calls FROM the MD110?.. What exactly do you mean?

Do you want to stop calls with certain CLI from establishing calls to the MD110 extensions. Do you want to bar extensions from dialling other specific extensions or external numbers. .. Please clarify.

Consider
NUTRP, TCMAP, LCR And Call Discrimination tables

Regards
Al



[red]Striker : My orders came through. My squadron ships out tomorrow, we're bombing the storage depots at Daiquiri at 18:00 hours. We're coming in from the North, below their radar.[/red]
[blue]Elaine : When will you be back?[/blue]
[red]Striker : I can't tell you that? It's classified.[/red]

 

[BrianQHong]

Say you are calling from 949-123-1234, I want to block you from calling into our office. that is what I mean by blocking selected incoming calls.

 

[HIREI]

In AXE-10 it calls A-number analysis. Version upto BC9, or BC10 have not this function. But may be now there is a feature something like A-number analysis?

 

[alchohaz]

You should be able to do something with the NUTRI table, it depends what you already have in it and the revision state of the PABX.

Try to translate the incoming number to a unplugged extension, predefined voicemail account or something along these lines... Sure that if you play with it you will get there in the end.

2     NUTRI     Number conversion initiate 
2.1   FORMAT 

 
CNVTYP =   Type of traffic case. 
For value, consult parameter description for number conversion. 
 
ENTRY =   Number to be converted. 
For value, consult parameter description for number conversion. 
& is permitted for this parameter. 
 
NUMTYP =   Type of number. 
For value, consult parameter description for number conversion. 
 
ROU   =   Route number. 
For value, consult parameter description for number conversion. 
If the parameter is omitted the number conversion will be made for the whole system. 
 
TARDST   =   Target destination number. 
For value, consult parameter description for number conversion. 
If the parameter is omitted the number conversion will be made for the whole system. 
 
TRC   =   Number of digits to truncate. 
For value, consult parameter description for number conversion. 
If the parameter is optional or not, see matrix under Function. 
 
PRE   =   Digits to insert at the beginning of the number. 
For value, consult parameter description for number conversion. 
If the parameter is optional or not, see matrix under Function. 
 
NEWTYP =   New type of number after the conversion. 
For value, consult parameter description for number conversion. 
If the parameter is optional or not, see matrix under Function. 
 
CONT =   Search continue indication. 
For value, consult parameter description for number conversion. 
If the parameter is optional or not, see matrix under Function. 
 
BCAP =   Bearer Capability. 
For value, consult parameter description for number conversion. 
If the parameter is optional or not, see matrix under Function. 
 
HLC =   High Level Compatibility. 
For value consult parameter description for number conversion. 
If the parameter is optional or not, see matrix under Function. 
 

2.2   FUNCTION 
The command is used for initiating number conversion and Bearer Capability/High Level Compatibility substitution. This command can also be used to change already initiated conversions. 

Number conversion can be made per system or at route level. If parameters ROU and TARDST are omitted the number conversion will be made for the whole system. By stating the parameter ROU the number conversion will be route dependent. Similarly, by stating the parameter TARDST the number conversion will be destination dependent. The route/destination dependent number conversion will override number conversion per system. 

It is possible to convert the received B-number, the sent connected number, the sent A-number, the received A-number and the received connected number. 
It is also possible to change the type of number using parameter NEWTYP at conversion of received A/connected number. 

The following variants of type of number are supported for public networks: 

Unknown public number 
International number 
National number 
Network specific number 
Local public number 
The following variants of type of number are supported for private networks: 

Unknown private number 
Local private number 
Level 1 Regional number 
At received B-numbers, the conversion can be done in two steps: 

-  Remove, add or change the international, national, local public, level 1 Regional prefixes or the route access code. 
 
-  Convert the internal directory number. 
In the first step, parameter CONT will indicate if conversion continues in the internal directory number table or not. If the conversion does not continue, the second step will not be done. 
 

If CONT is omitted, default value not continue is assumed. 

For Bearer Capability and High Level Compatibility substitution it is possible to substitute the Bearer Capability or/and the High Level Compatibility depending on the received B-number. 

The following variants of Bearer Capability are supported: 

SPEECH 
3.1 kHz audio 
64 kbit/s unrestricted 
64 kbit/s restricted 
UDI-TA (7 kHz) 
16 kbit/s unrestricted 
The following variants of High Level Compatibility are supported: 

NO TELESERVICE 
GRP 2/3 FACSIMILE 
TELETEX 
VIDEOTEX 
GRP 4 FACSIMILE 
TELETEX 64 
VIDEOTEX 64 
TIMELINK 
1/2 VIDEO 
In addition, it is possible to perform inbound conversion when requiring an internal numbering plan with extension numbers exceeding five digits. 
Internally, the system can handle a maximum of five digits for an extension number, but the user may dial more than five. 

This command is also used for public terminals validation working as remote extensions in ASB 501 04. In this case the A-number should be associated to the external party number, and command NUTRI is used with the following parameters: ENTRY = A-number, CNVTYP = 6, TRC = total number of digits of the A-number, PRE = remote extension number. 


--------------------------------------------------------------------------------

Parameters PRE, NEWTYP, CONT, TRC, ROU, TARDST, BCAP and HLC are optional. 
This is shown in the following matrix: 

CNVTYP  ENTRY  NUMTYP  ROU  TARDST  TRC  PRE  CONT  NEWTYP  BCAP  HLC  
0  m  m  o  -  o*  o*  o  -  -  -  
1  m  o  o  o  o*  o*  -  o  -  -  
2  m  m  o  -  o*  o*  -  o  -  -  
3  m  -  o  -  -  -  -  -  o *  o*  
4  m  -  -  -  o*  o*  -  -  -  -  
6  m  -  -  -  m  m  -  -  -  -  

 

Depending on CNVTYP the following NUMTYPs are permitted: 

    0  1  2  3  4  5  6  7  10  11  12  
CNVTYP  0  x  x  x  x  x  x  x  x      x  
  1  x  x  x  x  x  x  x  x  x  x    
  2  x  x  x  x  x  x  x  x        
  3                        
  4                        
  6

[red]Striker : My orders came through. My squadron ships out tomorrow, we're bombing the storage depots at Daiquiri at 18:00 hours. We're coming in from the North, below their radar.[/red]
[blue]Elaine : When will you be back?[/blue]
[red]Striker : I can't tell you that? It's classified.[/red]

 

[BrianQHong]

I still can't get it to work. Here is what I did:

NUTRI:ENTRY=17149991234,CNVTYP=6,TRC=11,PRE=2003;

2003 is a group hunt and goes into a voice mailbox that just hangsup.

If I have an Entry=9999,CNVTYP=0,NUMTYP=0,TRC=4,PRE=1234, which is the DNIS # that points to my office ext, Would that get processed first before it checks for the A-number entry?

 

[TRIDENT100]

CNVTYP=6, is for mob.ex. Try CNVTYP=0 and NUMTYP=2

 

[BrianQHong]

I tried the following and doesn't work:

NUTRI:ENTRY=9991231234,CNVTYP=2,NUMTYP=2,TRC=10,PRE=2003;
NUTRI:ENTRY=19991231234,CNVTYP=2,NUMTYP=2,TRC=11,PRE=2003;
NUTRI:ENTRY=9991231234,CNVTYP=2,NUMTYP=0,TRC=10,PRE=2003;
NUTRI:ENTRY=9991231234,CNVTYP=2,NUMTYP=4,TRC=10,PRE=2003;

This is driving me crazy.

 

[fcpli]

It won't work. The A-number conversion is meant for transit cases only.

 

[TRIDENT100]

Of course this will work:
eks:
NUTRI:ENTRY=1224098002,CNVTYP=0,NUMTYP=2,TRC=10,PRE=4303;

1224098002 is external number. When someone outside the PABX call this number they are rerouted to 4303. In my case is 4303 an external DEST use with IP Networking.

Regards

 

[cfrei]

If I undestand, you want:
called number is ZZZZ
if calling number is XXXX, called number is ZZZZ
if calling number is YYYY, translate called number to AAAA

Im not sure, but you can't modify called number according to calling number.

 

[whosrdaddy]

doing routing based on the A number is something the MD110 can't do (even not with nutri) you need an application on top of the MD110 to do this kind of stuff (like solidus)



--------------------------------------
What You See Is What You Get

 

[fcpli]

trident:

Try to read first what I wrote. As you see, this is a transit case, the call is not terminated to your MD.
What BrianOHong meant was this:
"Say you are calling from 949-123-1234, I want to block you from calling into our office"
Once more: IT WON'T WORK!

 

[TRIDENT100]

Ok maybe we are talking about two different things, what I ment was the following: you can convert received B-number to any number you like

Agree??[bigsmile

 

[whosrdaddy]

again,

the thread subject was "How to block an incoming call?", this has nothing to do with B-number conversion, were are talking about A-number blocking here...

this is something the MD110 simply CAN'T do!!!

--------------------------------------
What You See Is What You Get

 

[BrianQHong]

thanks for the info. I guess I'll have to use script manager. i already have script manager working for my acd groups.