Intercept handling on SX2k

[braindead2]

Can anyone tell me the difference between these to Intercept handling conditions below.. "what is the initial or fianl processing". I have a hotel where they want (9)999 calls from bedrooms to go to an EMG phone at reception and all other (9)999 calls from Admin to go out over the trunks.. I can do this using intercept handling with toll denial, but now all toll denial now goes to the EMG phone not just 999 calls which they don’t want..

Toll Denial - ARS Digits: Access to the external number dialed is denied because of the caller’s Class of Restriction (COR). The COR conflict arose in the initial processing of dialed digits (see COR Group Number in the ARS Assignment form).

Toll Denial - Route Digits:
Access to the external number dialed is denied because of the caller’s Class of Restriction (COR). The COR conflict arose in the final processing of the dialed digits (see COR Group Number in the Route Assignment form).

Any help appriciated..

braindead

 

[LoopyLou]

not exactly sure but basically its reads to me as toll denial because of the ARS leading digits dialed for initial processing part ( ie you can put a COR restriction in to the ARS digit form ) or toll denial based or the route ( i.e you put in a COR group in the route assignment ).

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[braindead2]

I know you can put a COR group number in the route and thats where the toll denial is achived from, i.e if your numbers in it you cant make the call. But you cant put a COR in the digit mod form?

I was more thinking if you dial 9 and your barred from dialling 9 then that would "Toll Denial - ARS Digits" but if you can dial 9 & 01xxx but not 07xxxx then that would be "Toll Denial - Route Digits:" but ill have to make some tests to find out..

Thanks for your help anyway its appriciated
Braindead

 

[LoopyLou]

You put the COR group against the route not in the DM form. Putting a COR group in the ARS digits dialed blocks that COR group from dialing those digits at all even if you are using a LIST. When you use a route and put a COR group against it, then you block dialing the number on that route only. So in the case of a list you might be blocked from the first choice route but not the second choice. That's why I typically don't put a COR group in the ARS form. Its more flexible.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[braindead2]

Thanks for that I totally understand it now, but toll denial conditions for route and ARS digits wouldn't have worked for what I was trying to achieve..

In the end i had to setup an ARS list containing two routes, the first route contains the normal outgoing trunk group which only the Admin phones have a COR to use this route so when they dial 9999 it will go out to the EMG service ok on the local trunks ok.. The guest room phones are barred from the first route in the list, so will try the second route in the list which contains an E&M trunk. I have set the E&M trunk interconnect restriction so that all calls are blocked from using this trunk and the call follows the intercept handling for Interconnect restriction and sends the call to the EMG phone with the guest name and number..

They don’t use the call blocking feature for the rooms at present, so I Just hope they don’t implement it in the future as all calls will then go to the EMG phone.. They only other way around this ithout useing the intercept handling would be to install a CEPT card setup as back to back DPNSS so the Guest phones would go out and back in and still display the guest name/number on the EMG phone.

Thank for help always appreciated..
Braindea2