ElKA ELKD not working for PRI route

[msunjai]

Hi,

Here is one very unusual problem I came accross long back, which I believe you might have also faced. So looking for some work around from you chaps.

I'm having Op61c with Rls25.40. We have several analog(XCOT)and digital(PRI)trunks.

user want to lock his extension (analog/digital) using ELKA/ELKD codes to avoid the misuse or say dial out from his extension in his absence. (As there is phone billing software installed which extracts reports on weekly and monthly basis and get charged to user if its not official call.)

The problem I'm facing is:- "after using ELKA/ELKD codes, access to analog COT-XCOT trunks only get denied and PRI trunks are available for dial out from the extension".

Can some one suggest me the peoper solution for this. Also, is this a drawback of electronic locking the extension using ELKA/ELKD codes.

I did manage to do some work around,

I configured one dummy XCOT route, configured one blank XCOT port as trunk and assigned it to that route as its member. Remember the trunk port defined and kept disabled and no analong line patch on MDF. Now this dummy analog route is defined "step" to PRI route which was causing the problem.

This is giving me the temperaory solution with few other problems raising the heads such as waste of one analog port on trunk card etc etc.

So did some work around using XLST/NCOS assigning which also seems to be temp. solution as there are other problems corping up.

Please suggest me the proper solution to overcome this problem as I'm jumbled now ...

Thanks in advance.

 

[johnpoole]

ELKA/ELKD work against a frl, is the frl on the dig routes the same as the one on your analog... sounds like you don't need hints to check that.. when i use locks, it turns off my ld ins int frl 5 and 6 but leaves 4 and below open for locals and 911 routing.. you might consider forced account codes + tod routing... 9 to 5 ncos 3 or higher don't need fac, after hours and weed ends, the users would have to use codes, that gives you the locout with certain users having a fac for bypass

john poole
bellsouth business
columbia,sc

 

[johnpoole]

to keep an analog trunk up, connect it to an analog ext, make it auto term to the pri route, then only one user will hit it and the other calls can be route with the rdb step command, for a work around for your dummy route

john poole
bellsouth business
columbia,sc

 

[janchundia]

Also, check the class of service that you are using when you active the electronic lock feature.
LD 21
req prt
type ccs_data

Javier

 

[msunjai]

Hi,

Yes, the FRL routes the same for digi set as the one on for analog..., the COS is also set properly the CCS data as well.

Certainly, FAC/TOD routing was the first workaround in my mind, but as the user are leaving there desk often and keeps roaming during the working hrs. the requirement of elka/elkd arised to avoid the misuse of extn and the option of TOD routing ruled out.

The analog line is purposly not connected to the trunk port & is disabled manually which works fine to step to the other route.