Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

LCR And conflicting numbers 1

Status
Not open for further replies.

fouesnant

Technical User
Aug 31, 2005
331
FR
Hi all

I have some problem to solve a particuliar problem on customer site.
01234xxxxx is the DID range of the exchange. If the users dial this number, in LCR, tab=ENT I can truncate the leading digits to make an internal call.

Now 012 is also a public network access number for services.

If I set in ENT that 01234xxxxx is conflicting, calling internal number will work only if I specify the complete number and 012 set in DNT1 will work only if I press # or and extra digit to place the call.

Is there a way to manage the conflicting number in a better way ?
 
Hi' in ENT set ENTRY=01234 TRC=5, don't use CONF ( this is not a conflict number ) and in DNT1 or 2 set ENTRY to 012.
 
Hi fouesnant,
is really 01234 public number of MD? When you put this number in ENT, which number is LCR access code (LAC)? It looks, that 0 is LAC and public number is 1234. And public network access number is 012 or 12?
 
Please give us a complet example to use the conflict-parameter
 
Hi' from Alex:
CONF=Y
Indication whether the number is a conflict number or not (conflict numbers are numbers with the same leading digits but with different number length, e.g. if both 12 and 123 are valid numbers they are in conflict and a time supervision has to be performed after the second digit in order to see if any more digits will arrive).
So:
LCDDI:ENTRY=12,TAB=ENT,CONF=Y;
LCDDI:ENTRY=12,MIN=2,MAX=3,CONF=Y;
And then there is a ASPAP ( I don't remember the number ) to set the time-out supervision for more digit, here after 12.
I have seen this conflict number both in Hong-Kong and south England.
 
Hi all

I will precise the context; national numbering plan is 10 digits starting always with 0, ie 01234xxxxx, where xxxxx is the numbering plan of MD110.
12 is also used by the public network to access services.

Now 0 is used by the MD as LC code.
My problem is when a user makes a mistake and dial 01234xxxxx (instead of 001234xxxxx) and then due to LCR, or DEST or whatever, this is sent to the public network as 1234xxxxx. Now the network is smart and recongine 12 in the beginning of the number and route the call to the requested service center.

Mundus, I have tried your configurations, but it does not work
My problem is to set in ENT at least 01234 and trunk the 5 first digits in order to have a chance to reach the xxxxx number which is internal.
But, by doing this, 012 cannot be anymore analyzed by the MD, even if indicated as conflicting number.
Doing the opposite, enter 012 in ENT, make possible to dial out, but not internally.

I guess your configuration works when the conflicting number are both external, but what about internal and external?
 
Hi' fouesnant, then the ENT table should be 001234 for off net-to-on net and CONF=N, and as I see it - it's not possible to let the MD see that a user has dialled wrong number 01234xxxxx instead of 001234xxxxx, but maybe some "guru" out there have a solution !
 
Hi
try following for conflict numbers:

example from my exchanges

Area code for LIM
lcldi:lim=1,ac=8,dest=7,

NLT
lcddi:tab=nlt,entry=012,min=3,max=4,conf=y,acf=y;


It means 012 is conflict number,whem min number reached, then insert own area code after least cost code
(number is now 0812)


Now you can make anything you want in DNT1 or DNT2.


I have only two exchanges,so i made two extensions, number 123 and 0123.

External DEST = 7

FDT
FRCT TZONE PRE
1 1 7
2 1 70


DNT2
ENTRY TRC PRE ACCT FRCT TOLL CBCS BTON TNS OSA
0 1 0 1 111111111111111 0

In DNT2 leading LAC 0 is truncated, FRCT=1 is DEST 7 with SRT=2


DNT1
ENTRY TRC PRE ACCT FRCT TOLL CBCS BTON TNS OSA
08 2 0 2 111111111111111 0

LAC 0 and AC 8 is truncated FRCT=2 is DEST 7 with SRT=2, next 0 is send out.


I think TIMTOWTDI and better try it in directly in your MD.

 
Hi cfrei

Many thanks for your help. I vote a star for you.
I can perform my analysis correctly now.

Best regards
 
sorry, I´m to stupid, thatswhy a few questions:

1. Question: What is your lc-Code in Nadap?

"Area code for LIM: lcldi:lim=1,ac=8,dest=7;"

2.Question: I think "Area Code" is the prefix code for your own town, correctly? For Berlin ac would be 030, right? 7 goes to normal public route?

"NLT lcddi:tab=nlt,entry=012,min=3,max=4,conf=y,acf=y;"

"It means 012 is conflict number,whem min number reached, then insert own area code after least cost code
(number is now 0812)"

3.Question: 8 is inserted by acf=y, right? Why max=4?

"I have only two exchanges,so i made two extensions, number 123 and 0123"

4.Question: What doe it mean, you have two exchanges with two extensions? Which is dest for Exchange1 and what is dest for Exchange2 and how the PBXs are linked - by public lines or private lines?

External DEST = 7

FDT
FRCT TZONE PRE
1 1 7
2 1 70

5.Question: to what for routes go this two pre?

DNT2
ENTRY TRC PRE ACCT FRCT TOLL CBCS BTON TNS OSA
0 1 0 1 111111111111111 0

In DNT2 leading LAC 0 is truncated, FRCT=1 is DEST 7 with SRT=2


DNT1
ENTRY TRC PRE ACCT FRCT TOLL CBCS BTON TNS OSA
08 2 0 2 111111111111111 0

LAC 0 and AC 8 is truncated FRCT=2 is DEST 7 with SRT=2, next 0 is send out.

 
Hi Lalrl,

I can may answer your question I have programmed the stuff in Lab and on custoemr site :
1/My LC code in NADAP is 0.

2/I don't use Area code over the public network. So DEST=7&70 and area code are just ways to detect where to route the call inside LCR. I use the number sorted out from the LCR with a DEST and I make the necessary TRC and PRE to send only what I want, in my case 12 for network service or 012xxxxxxx for network user, either private or public.

3/In my case Max is not equal to 4, but to 10, to comply with the national numbering plan length. In fact with 012, I need to detect only 2 length, either only 3 digits, or 10 digits, but it is up to you for that according to your need and where the call need to be routed.

4/I have made the same test as CFREI
Connect 2 exchanges over line, what ever the protocol is, public, privet, ISDN, QSIG.... just to verify that the programming works, and one public connection.

It could be represented as
Ext A Ext B 2 digits service
Exchange A ---ISDN---Exchange B ---ISDN--- Public Networ
ISDN ISDN 10 digits user
4 digits LCR Programming


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top