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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Block outgoing number

Status
Not open for further replies.

bdeal4122

Technical User
Dec 19, 2014
105
US
How would I go about programming a user so they can block their outgoing number?
Also, once it's enabled, what would they dial? We dial 9 to get out, and 9 1 to get an outside long distance line.
I changed CLS to CLBA on my phone and tried dialing 91*67XXXXXXXXXX but right after I dialed the 7, it went to busy.
I'm sure this is very simple, but I'm not sure what's wrong.
Thanks.
 
CLBA is for blocking on ALL calls from that phone.
*67 is for blocking per call and you would dial *6791xxxxxxxxxx. Assuming that *67 is your Flexible Feature Code for blocking.
 
Thanks for the reply. How would I check to see what the Flexible Feature Code is?
When I dial *6791 I get a busy signal. I don't know if this makes a difference, but with our company, when you dial * followed by a 3 digit number it dials a WAN line at one of our other locations. Will that make a difference?
You were right about CLBA blocking no matter what, however, I'm not sure that's what my client wants. It's nice to have the option though.
 
to view all the feature codes,
LD 57
REQ PRT
TYPE FFC
CODE ALL
search for your code *67 ,I am sure it will be infront of CPP option.

take a print of the route in LD 21
look for the option TCPP, it's value Will be YES.
dialing your WAN codes shouldn't make any problems
 
I printed all the codes and didn't see cpp or *67. Does this mean *67 isn't an option and how would I change that?
Here's a print out of it:
CUST 00
FFCT NO
ASRC
AUTH
AWUA
AWUD
AWUV
CDRC
CFWA #1

CFWD #1

CFWV
COND
CPAC
CPRK
CSHF
C6DS
DEAF
DPVS
ELKA
ELKD
PLDN
GRPF
HOLD #4

CFHO
IMS
MNTC
MTRC
OVRD
ITXX
PUDN
PUGR
PURN 73

RCFA
RCFD
RCFV
RDLN
RDNE
RDSN
RDST
RGAA
RGAD
RGAV
RMST
SCPC
SPCC #2

SPCE
SPCU #3

SSPU *

TFAS
TRMD
TRVS
USTA
LILO
NRDY
GHTA
GHTD
SADS
SAEN
SALK
SAUN
EOVR
ATDA
ATDD
CWGA
CWGD
MSBA
MSBD
MWUA
MWRA
MWUD
ADMN
ICFA
ICFD
ICFV
USCR
INST
USER
BNRA
BNRD
CCFA
CCFD
OCBA
OCBD
OCBV
CPP
CPPO
CFDD
VTLN
VTLF
PCAA
PCAD
PCAV
MTRN
MCFA
MCAN
MCOM
MTGL
 
Take another look. CPP is there but it does not have a code programmed.
Also suggest you look at the Features and Services book under Calling Party Privacy.
 
when in LD 16 TCPP is given the option YES then this
*67 is assigned as by default .you can read this in the admin manual under LD 16 . if you want to change that, go to LD 57 and give the value to CPP. the code will be changed
 
Here's an interesting update, the client does want all outgoing calls blocked, but setting the class of service to CLBA does not block all outgoing calls on that extension...it blocks calls to local numbers, but not long distance calls. We dial 9 to get out and 9+1 to get a long distance line. I dialed my cell using just the 9 and the call was blocked. I called my cell again using 9+1 and the number was there.
Is there any other setting I can change to also block when we dial long distance?
 
CPP has nothing next to it so I tried to change cpp to *67 but keep getting the error sch8893.
Here is what I did:
In ld 57,
req chg
type ffc
cust 0
ffct
code cpp
cpp *67


SCH8893

Any suggestions? I'd love to block outgoing numbers all the time, but if I can't figure that out, I'd like to make it so they can at least do a *67.
 
hi,
CCP is already *67 and you are writing the same code again in the changing option. so it is giving the error. you should try a different code here for CPP prompt.
 
Thanks for the response. If this is already programmed in the system, how come it's not working? I dial *67, then 9 and it immediately goes to a busy signal. Is there anything else I can check?
 
The reason you get the SCH8893 is because * is already programmed as the FFC for SSPU (System Speed Call User). You can't have *67 for CPP unless you change SSPU.

Regarding CLBA not working for long distance calls, if they are routed over a trunk route that does not have CPP YES in the RDB then it won't work.

Suggest you look at the Features and Services book under Calling Party Privacy.
 
I just looked through the phone system books and they tell me what you're telling me. *67 should work. I found it said for 500 model phones to dial 1167...I tried that and got a busy signal too.

I don't understand what this means:
[highlight #FCE94F]Regarding CLBA not working for long distance calls, if they are routed over a trunk route that does not have CPP YES in the RDB then it won't work.[/highlight]

How can I find out if the trunk route has cpp yes in the rdb? If it doesn't how can I change that?

I'm sorry, but I know enough about this phone system to be dangerous, and with being the sole support person everyone comes to me for stuff like this.

Our support sucks, so I can't go to them with this.
 
take print of the route for every long distance code which you are using for dialing the outward dialing like your cellphone.... which is 9, or 91.

LD 21
REQ prt
type RDB
Cust 0
route just press enter
acod here give the code
....
complete print will be display for the route..

Now look for the TCPP option, whether it is YES or NO.

if it is NO,,, then that is the reason of not blocking the CLBA class user on long distance calls.

to change this to YES,
LD 16
REQ CHG
TYPE RDB
ROUT give here the number of the route.
.
.
.
TCPP YES
.
..
.
press enter until the REQ prompt again comes.
that's all
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top