colpritt

[quote=colpritt]

And, this is a new COR I created, as you can see IDENTICAL to the End User COR...... and it DOES work.

CLASS OF RESTRICTION

COR Number: 24
COR Description: test

FRL: 3 APLT? y
Can Be Service Observed? n Calling Party Restriction: none
Can Be A Service Observer? n Called Party Restriction: none
Time of Day Chart: 1 Forced Entry of Account Codes? n
Priority Queuing? n Direct Agent Calling? n
Restriction Override: none Facility Access Trunk Test? n
Restricted Call List? n Can Change Coverage? n

Access to MCT? y Fully Restricted Service? n
Group II Category For MFC: 7
Send ANI for MFE? n
MF ANI Prefix: Automatic Charge Display? n
Hear System Music on Hold? y PASTE (Display PBX Data on Phone)? n
Can Be Picked Up By Directed Call Pickup? y
Can Use Directed Call Pickup? y
Group Controlled Restriction: inactive

CLASS OF RESTRICTION

MF Incoming Call Trace? n
Brazil Collect Call Blocking? n
Block Transfer Display? n
Block Enhanced Conference/Transfer Displays? y





Station Lock COR: 24

CLASS OF RESTRICTION


CALLING PERMISSION (Enter "y" to grant permission to call specified COR)

0? y 12? y 24? y 36? y 48? y 60? y 72? y 84? y
1? y 13? y 25? y 37? y 49? y 61? y 73? y 85? y
2? y 14? y 26? y 38? y 50? y 62? y 74? y 86? y
3? y 15? y 27? y 39? y 51? y 63? y 75? y 87? y
4? y 16? y 28? y 40? y 52? y 64? y 76? y 88? y
5? y 17? y 29? y 41? y 53? y 65? y 77? y 89? y
6? y 18? y 30? y 42? y 54? y 66? y 78? y 90? y
7? y 19? y 31? y 43? y 55? y 67? y 79? y 91? y
8? y 20? y 32? y 44? y 56? y 68? y 80? y 92? y
9? y 21? y 33? y 45? y 57? y 69? y 81? y 93? y
10? y 22? y 34? y 46? y 58? y 70? y 82? y 94? y
11? y 23? y 35? y 47? y 59? y 71? y 83? y 95? y

SERVICE OBSERVING PERMISSIONS
(Enter "y" to grant permission to service observe the specified COR)
0? y 12? y 24? y 36? y 48? y 60? y 72? y 84? y
1? y 13? y 25? y 37? y 49? y 61? y 73? y 85? y
2? y 14? y 26? y 38? y 50? y 62? y 74? y 86? y
3? y 15? y 27? y 39? y 51? y 63? y 75? y 87? y
4? y 16? y 28? y 40? y 52? y 64? y 76? y 88? y
5? y 17? y 29? y 41? y 53? y 65? y 77? y 89? y
6? y 18? y 30? y 42? y 54? y 66? y 78? y 90? y
7? y 19? y 31? y 43? y 55? y 67? y 79? y 91? y
8? y 20? y 32? y 44? y 56? y 68? y 80? y 92? y
9? y 21? y 33? y 45? y 57? y 69? y 81? y 93? y
10? y 22? y 34? y 46? y 58? y 70? y 82? y 94? y
11? y 23? y 35? y 47? y 59? y 71? y 83? y 95? y

It makes no sense.... what do you think?!?! Thank you!!!!

koelemon

[quote=colpritt]I see one difference, on their COR they cannot call COR 15 and yours can, that could be big with this depending on what COR 15 is used for. Change it to yes and see what happens

__________________
"There are only 10 types of people in the world,
those who can read binary and those that cannot."

PBXtech.info

 

colpritt

Oh my gosh, I can't believe I (and everyone who looked at the printouts for me!) missed that!!!! Yep, that made a difference when I changed it. But... that's another whole can of worms.... 15 is the COR for trunks. I don't want all users to have access to that! And... why would that make a difference? If the users can access the trunk group to make regular calls? What do you think? Thank you so much!!!

nexSIP

I put my $5 on this problem:

Station Lock COR: 1
CLASS OF RESTRICTION

CALLING PERMISSION (Enter "y" to grant permission to call specified COR)

15? n

koelemon

Well, here is my take on it and anyone please chime in to correct me if I am wrong...

The COR 15 for trunks will allow them direct trunk access if you have them trying to do a facility access test (which you can restrict also onm the COR on page one instead) or TAC (which I would keep at no on the trunks anyway until you need to test something). the reason they can make regular calls is because they are not necessarily accessing the trunk "directly" but rather through ARS which allows it to go out, the reason it fails I think during remote coverage is that then you create a "3 way COR check" scenario where everyone's COR is validated to make the call work. I hope that makes sense...hopefully someone can explain it better if it didn't! :)

__________________
"There are only 10 types of people in the world,
those who can read binary and those that cannot."

colpritt

Yep, that makes sense.... how do you think I should fix it? Seems like allowing the user COR to call the trunk COR is risky.... thoughts?

PBXtech.info

 

nexSIP

turn this off in the COS "Restrict Call Fwd-Off Net" which is dangerous also.
We have a handful of users who we do this for. I create a VDN/Vector that will route to thier home number. then its being controlled. no fraud.

penelope

I just ran into this denial event 1756 today where ONE user in a pilot group of people who are forwarding their extensions to another system could not receive calls from an outside caller either DID or toll free on different truck groups. The users are forwarding their calls to another trunk group that goes to the other system.

I compared the COS on his station and that's where the problem was even though the error message said it was a COR restriction issue. He had a different COS than everyone else and I changed the following and it worked.

Restrict Call Fwd-Off Net n
Extended Forwarding All y
Extended Forwarding B/DA y
Trk-to-Trk Transfer Override y

__________________
Penelope