Alcatel Unleashed

I am trying to block calling to all area codes information, or 1XXX5551212, but it does not seem to be working. I created a new rule in the discriminator 0.
Node Number (reserved) : 10
Instance (reserved) : 1
Instance (reserved) : 1
Discriminator No. : 0
Call Number : 1XXX5551212

Area Number : 7
ARS Route List Number : 0
Schedule Number : -1
Number of Digits : 11

I have also tried the following rules as well

Node Number (reserved) : 10
Instance (reserved) : 1
Instance (reserved) : 1
Discriminator No. : 0
Call Number : 1XXX555

Area Number : 7
ARS Route List Number : 0
Schedule Number : -1
Number of Digits : 7 or 11

None of those rules are working. I have no phones assigned in area 7 and no ARS route list.

Anyone have any idea how to restrict calls to XXX5551212? Not sure why the wildcards (XXX) are not working.

Thanks

Check at first with number without X - f.e. declare whole dialed number.
You will check management:
- seizure prefix not personal - private access COS used instead of public access COS;
- no problem with Public network COS - f.e. when user in Hunt group or managed rights for state "day" but entity state=night;
- no problem with entity/discr. selector - used right real discriminator.

If I create area code + 555 or area code + 555 1212 (correct number of digits dialed) the call is rejected as it should be.

Private Access COS is 1 for all public NCOS

We do not manage calls based on day or night states

As far as I can tell I am using Discrimintaor Selector 0 which = real discriminator 0.

I do not want to have to create every area code + 555 top restrict these calls. I thought XXX + 555 would work.

Not sure what to check now?

Was problem with "W" - The function of ?W? in the discriminator rule is not working (from read.me g1.503.21 and in R9 was the same problem).
May be with X the same - SW problem? I cannot check (no PBX access at this moment), may be someone can check this?

Yes vad, you are rigth. - OXE has big problems with wildcards in discriminator.
In Release 9.1 you can use it. But in some situation the config works only after a reboot.

In our OXE this is configured, but is was a long, long way

Best regards
smileyman

So my first step would be to try a double bascul? I have the programming there with XXX but it does not work.

Please advise.

Thanks

Yes, a double bascul is a good idea. - But XXX dosn't work.
The result of my tests is: X dosn't work at first and last digit.
Use instead 1X1, 1X2, 1X3, 1X4, 1X5, 1X6, 1X7, 1X8, 1X9, 1X0, 2X1, 2X2, 2X3and so on.

In my case i use 1XX1, 1XX2, 1XX3, ...; 2XX1, 2XX2, 2XX3, ...; 3XX1, ... and 1XXW, 2XXW, 3XXW, ... to select between numbers with 3 digits and with 4 digits.

Yes the list is not shot, but with Excel and Import-function no problem and it works (after a bascul)
By the way: If you have an typing error and you can't delete the entry - a bascul is the solution

Best regards
smileyman

Tried adding the rules I described above and then performed a double bascul. Ther rules are still not in effect.

Not sure what to do next. I triple check the entity, discriminator selector and discriminator rules, even used lookars i to make sure I was taking the correct route.