Hi
Please can you help?
We want to withhold CLI on outgoing calls. Until recently we did. Then (without us doing anything) suddenly the CLI was going out.
We have CLIR (Calling Line Identity Restriction) on our ISDN trunks but the number is still going. Sometimes the base number of the DDI range X000 and sometimes with the DDI number included.
We found what we thought might be the cause but that rsults in the message "secret identity" when you dial 9.
As usual BT blame NextiraOne and NextiraOne blame BT and menatime our CLI keeps going out.
Can anyone help?
Withholding CLI on outgoing calls
Re: Withholding CLI on outgoing calls
Check with "t3" trace your SETUP. If you send your calling number like 21 a1 : 1234567 - PBX send number 1234567 and "secret identity" information.
If you see number 1234567 on called set - ask your provider why "secret identity" feature ignored.
If you see number 1234567 on called set - ask your provider why "secret identity" feature ignored.
-
Ph1lfy
Re: Withholding CLI on outgoing calls
Hi Vad, thanks for that bt the secret identity is currently being used as a workaround.
We want to know the vanilla way to withold CLI and test because carrier says PCX is causing the CLI to go even though they have CLIR pplied to the ISDN trunks. Usual situation where PBX and carrier blame eachother.
We suspect the carrier as no changes were made to the PBX to cause the number to suddenly start going.
We just want to withhold our number altogether.
I guess what we are asking is where we withhold the CLI so we can check if that parameter is correct or not?
Appreciate your time on this. Thanks very much
We want to know the vanilla way to withold CLI and test because carrier says PCX is causing the CLI to go even though they have CLIR pplied to the ISDN trunks. Usual situation where PBX and carrier blame eachother.
We suspect the carrier as no changes were made to the PBX to cause the number to suddenly start going.
We just want to withhold our number altogether.
I guess what we are asking is where we withhold the CLI so we can check if that parameter is correct or not?
Appreciate your time on this. Thanks very much
-
Ph1lfy
Re: Withholding CLI on outgoing calls
I had BT tech support in re the CLI issue. They quoted their SIN which refers out to ETSI Standard 300 091.
They also traced calls with secrety identity on and off of the entity
With Secret Identity on no display goes to line and the field Calling Party Number and all its parameters are not there at all.
With Secret Identity off the display goes. The Calling party Number field is there with it`s parameters including "presentation allowed." BT says that this overides the CLIR at the local exchange but I`m not so sure as the standard says it can be changed at the local exchange (FE2).
Then NextiraOne found a parameter to change to stop the CLI going out without the CLI.
They also traced calls with secrety identity on and off of the entity
With Secret Identity on no display goes to line and the field Calling Party Number and all its parameters are not there at all.
With Secret Identity off the display goes. The Calling party Number field is there with it`s parameters including "presentation allowed." BT says that this overides the CLIR at the local exchange but I`m not so sure as the standard says it can be changed at the local exchange (FE2).
Then NextiraOne found a parameter to change to stop the CLI going out without the CLI.
-
tot3nkopf
- Alcatel Unleashed Certified Guru
- Posts: 4058
- Joined: 02 Feb 2006 10:41
- Location: Germany & Romania
- Contact:
Re: Withholding CLI on outgoing calls
Old topic however I found this problem for an installation with country set to UK.
In all other systems (with other countries configured) CLIR works like this:
| IE:[6c] CALLING_NUMBER (l=11) -> 01 a1 Num : 123456789
| IE:[70] CALLED_NUMBER (l=2) -> 81 Num : bla bla
CLIR is activated and number is sent (a1).
When CLIR inactive normal operation:
| IE:[6c] CALLING_NUMBER (l=11) -> 01 81 Num : 123456789
| IE:[70] CALLED_NUMBER (l=2) -> 81 Num : bla bla
CLI presentation allowed (81)
Everything fine.
In UK node when CLIR is activated CALLING NUMBER IE is not sent at all.
For CLIR inactive everything fine.
Which is the system parameter responsible for this behavior?
In all other systems (with other countries configured) CLIR works like this:
| IE:[6c] CALLING_NUMBER (l=11) -> 01 a1 Num : 123456789
| IE:[70] CALLED_NUMBER (l=2) -> 81 Num : bla bla
CLIR is activated and number is sent (a1).
When CLIR inactive normal operation:
| IE:[6c] CALLING_NUMBER (l=11) -> 01 81 Num : 123456789
| IE:[70] CALLED_NUMBER (l=2) -> 81 Num : bla bla
CLI presentation allowed (81)
Everything fine.
In UK node when CLIR is activated CALLING NUMBER IE is not sent at all.
For CLIR inactive everything fine.
Which is the system parameter responsible for this behavior?
