Realitis DX Route Restriction 1

[telecoman]

Hello all,

I am installing a second user Realitis DX running Issue 6.1 software.

Try as I may, I can't get the route restriction to work.

The time of day route restriction feature is turned off.

The trunk group access for exchange trunks is turned on and the appropriate route restriction table is associated with the TAC of the extension.

Turning off TGA does produce restriction for all routes on all extensions using this TAC.

I've looked in the feature table, at feature codes, class of service definitions and system parameters but still can't get normal 24hr route restriction to work.

Could anybody help please before I go whiter than I already am?

Any help is highly appreciated.

Best regards to all,

Telecoman.

 

[happymal]

This one is a minefield, I have worked on TOD barring many times over the years and every time I recieved another request to set one up the learning curve started again.....

First in the feature table (LFT A) TOD=Y, if not AFT TOD Y.

Next is LDAP A which will give you all the patterns and PE (exception days) WARNING...... it is best to LEXD to check what days are set before you go any further, Before the call 'we cannt dial any where'. This can be deleted by REXD...

Back to LDAP at the end of this print it will give a current time band, its then into the learning curve to find out which Pattern is what every day you are working on it, Monday is not P1, this can be found by changing the STD (Time and Date). You must have already created Route Restriction tables and COS zones to test this, ARRT/LRRT/LACR/RACR.

Time bands can be created and deleted by CTMB/DTMB.

http://hipath.custhelp.com/DX_files/HiPath_DX_EP_V9new/EP v9.0/description/features/routeing.htm#tod

Try reading this gobleygook, it may help. but it is still a deep subject and unless you are working with it regulary it is trial and error till you get it right.

Good Luck....

 

[telecoman]

Hi Happymal,

Thank you very much for your very quick reply.

I am really after 24hr. route restriction, rather than TOD route restriction.

However, activating the TOD feature, route restriction still did not work.

I then checked LACA and found that least cost routing was activated. I de-activated LCR using RACA and lo and behold TOD RR started to work. I then de-activated the TOD feature with LCR still de-activated and found that 24hr RR now worked, as I wanted.

So now, I appear to have solved the problem.

Just a couple of things though. There is a LCR parameter in LTME (list trunk main group - extended) which in my case was selected to N. What effect does this have and how does it fit in with the LCR option in LACA? Secondly, it would appear that least cost routing is not possible together with route restriction - is this true?

Many, many thanks for your help Happymal and I look forward to possibly hearing from you again or anybody else who cares to join in the debate.

Very best regards,

Telecoman.

 

[happymal]

Have a look at what carrier routes you have LCRT A ,,,
Also LCRR (List carrier route restriction tables).

These are the same tables that are in LACR, a common mistake is that people switch on LCR and the comment is 'Why can I still dial out' The answer is what ever is in LACR .... Should be in LCRR on all of the carrier routes. If in your LACA table code 9 is set to LCR all calls are then controlled by the LLDT Table and List (LRL).. so ....
LLDT > Zone ? (Same zones as COS)> digits (say 0771 mobile) The aswer is Voice list ? Data List ?? ... next is LRL >List ? answer is in routes say 1 2 3, route 1 being first choice route 2 being second choice etc. (6.1 can have a max of 4 routes, it went to 99 on ver 8)...
So First choice route 1 LCRT 1

CR NEP MDT SEND FREQ1 SSS FREQ2 STS FREQ3 SLS OUT CIL
CSI
DEPT




CR= Carrier route number NEP= Network exit point MDT= Modify digit table, these are the important ones, the rest dont count unless you have some specialist carrier.

This is where LCRR comes in, these must have the same LRRT tables in it as the LACR for correct allow/barring. and the same would count for routes 2/3/4 or 99 if ver 8 and above.

I hope this makes it a little clearer. If you require more guidance let me know and I will set up a dummy email for contact and then delete it. Mal.