new cor, can't call out 2

[papagigo1]

I built a new cor (15) for use with just off prem extensions over the intranet H323 to Multitech units. Station to station works great but I can't call out! I dial 9 then the number and get waved off !
I matched cor15 with cor4 which is used for everyone here in the building and if I assign cor4 to these remote stations they work fine, any idea what I'm missing on cor15?

Mike in NH

 

[definityandcmuk]

can you paste the COR setup onto a post?

Check calling party restriction
Check the FRL
Check the RCL setup
Also, maybe check page 3, are any fields set to N?

 

[papagigo1]

This is COR 15



display cor 15 Page 1 of 4
CLASS OF RESTRICTION

COR Number: 15
COR Description: remote station 911 deny

FRL: 4 APLT? n
Can Be Service Observed? n Calling Party Restriction: none
Can Be A Service Observer? n Called Party Restriction: none
Time of Day Chart: 2 Forced Entry of Account Codes? n
Priority Queuing? n Direct Agent Calling? n
Restriction Override: all 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

display cor 15 Page 2 of 4
CLASS OF RESTRICTION

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


Station Lock COR: 15
Outgoing Trunk Disconnect Timer (minutes):

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? n
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

 

[4merAvaya]

Your Time-of-Day setting in the COR shows 2. Does that match the original COR?

Kevin

 

[papagigo1]

No, it doesn't match cor 4, which works. The time of day #2 was added to deny 911 calls from these remote locations. I think you hit on my problem..But I'm not sure where to go from here? I still need to stop 911 calls.

Mike in NH

 

[definityandcmuk]

what does your "display partion" table look like?

do you deny the 911 is ARS in PGN 2?

is it wise to deny 911 calls?

 

[papagigo1]

definityandcmuk

These extensions are used as FX lines in remote locations. It is wise to deny 911 calls from these extensions that will come from a CM2.1 in another state. This is what I'm trying to stop. At the remote sites there are numerous local pots lines that can be used for 911.

911 calls are denied in ars for PGN#2

change partition-route-table 2 Page 1 of 1
PARTITION ROUTING TABLE

Routing Patterns
Route
Index PGN 1 PGN 2 PGN 3 PGN 4 PGN 5 PGN 6 PGN 7 PGN 8
----- ----- ----- ----- ----- ----- ----- ----- -----
2 2
3 3
4 4
5 5
6 6
7 7
8 8 deny
9 9
10 1
11 11
12
13
14
15
16

 

[4merAvaya]

Change the COR 15 FRL entry to 3. In the Route Pattern for 911 have the FRL set to 4. You can't place the call unless the caller's FRL is equal to or greater than the FRL on the Route Pattern.

Kevin

 

[papagigo1]

Kevin,

If I change the FRL on COR15 to 3, it will be less than FRL4 for route pattern 8. So this will end up as less than, not greater or equal to?

Mike

 

[irisngen]

You dont have anything under PGN 2 which is what that COR 15 is trying to use. you only have a deny for P8.

 

[papagigo1]

That was it !!! Thanks to everyone!!