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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MD110 configuration 2

Status
Not open for further replies.

cspectra

Technical User
Apr 30, 2007
56
US
I am assigned to figured out the problem with our Ericsson MD110 BC12. I know almost nothing about PBX, but I have ALEX, and could not do much with it since I am a novice in this field. The old expert left and took all document with him, I guess.
In general, the voice is OK. But we got some problem dial in and out. The provider told us that they could not receive any information from our side except the called number (B-party). Besides, the CLI number they got on their test phone is the CLI they assigned to our main PBX, 999-9999-9999! They said the problem is on our side.
Could anybody help me with this. Thanks
 
You can set the CLI to ON or OFF,

however, it depends on what your carrier does with the calls.

If the Carrier has been instructed not to display CLI it will withold it, if they will display it, it will display the first number in the DDI range: example

DDI range is 01256 123000-1234000
your extension is 3156

so your DDI number is 01256-123156

The caller will have displayed 01256-123000
 
Thank you for your prompt response.
The problem is, according to them, the PBX never sent any B-party number out. I'd like to know how to check and turn on this feature so that all possible call-information sould be sent out to trunk line.
I am studying the PARNUM list, but not sure which one relates to this, and which command will be used to change this. Put up with me please!
 
cspectra (TechnicalUser) 1 May 07 10:20 WRIT:
>Thank you for your prompt response.
>The problem is, according to them, the PBX never sent any >B-party number out. I'd like to know how to check and >turn on this feature so that all possible call-information >sould be sent out to trunk line.
>I am studying the PARNUM list, but not sure which one >relates to this, and which command will be used to change >this. Put up with me please!

What type of trunks do you have? If they're not ISDN or IP, you won't be sending out any calling party info anyway.

The calling extensions have to be allowed to present their internal number to the network -- enabled in the ADC parameter for the extension category info. (ADC bit 9 for analog and ADC bit 10 for digital)

You'll need to use the number translation feature and RONDI to build out the rest of the public number as it goes out to the network.

And, as stated above, your circuit (if ISDN) has to be enabled by the carrier to pass the calling party info to the rest of the network.

Good luck,

Dave Strang

 
dstrang1; I post wrong info; the A-number is not sent out to the destination, not the B-number. The only trunk is ISDN.
There is only 1 route in the system. How many routes can we create? And I am not sure how to check for the setting of the calling extension. Could you help please. Thanks
 
To check an analog extension: EXCAP:DIR=xxxxx;

In the printout, under ADC - the last bit should be a one.

To check a digital extension: KSCAP:DIR=xxxxx;

In the printout, under ADC - the tenth bit should be a one.

The best way to find out what your switch is sending out is by monitoring the D-channel messages with a protocol analyzer.

Good luck,

Dave Strang
 
dstrang1.
Thank you for your tips. I made it work, and the Extension number shown on the trace for call setup going out. However, it is only its extension, no PBX number.
I think nobody ever set this up. Could you tell me the sequence and command to set this up. Please.
Again, thank you very much.
 
check your outgoing routes with RODDP:DEST=ALL;
then assign prefix to the outgoing route with RONDI.

small example:

suppose we have DDI range 123 3xxx (3xxx = extension)
RONDI:ROU=X,EXNOPU=2-123;
the '2'-123 stands for national number. if the PBX sends out unknoxn number format, change 2 into 0 (so 0-123)

/Daddy

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
You can use number conversion and route number data to build out the rest of the calling number. You can actually do it all in number conversion....

The command is :NUTRI:, the parameters you'll be concerned with are entry, cnvtyp, numtyp, and pre

Look in ALEX, Operation and Maintenance,ACS under Number Conversion for info regarding the command and the above parameters.

Good luck,

Dave Strang
 
small NUTRI example

suppose we have extension 3xxx series:

NUTRI:ENTRY=3,CNVTYP=1,NUMTYP=10,pre=12345;

/Daddy

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
Thank dstrang1 and whosrdaddy.
The conversion for both received B-num and sending A-num is working now. However; I am not sure what RONDI does for the number to call out? Besides, can you tell if I can make more routes with one ISDN trunk, in which all lines are tied to the existing rou?
I'd like to create all routes, if neccesary, for international, nat, unknown, and subscriber; could that be possible with just one route per different destinations?

Thank you again.
 
cspectra (TechnicalUser) 4 May 07 10:31 sed:
>Thank dstrang1 and whosrdaddy.

You're welcome.

>The conversion for both received B-num and sending A-num >is working now. However; I am not sure what RONDI does for >the number to call out?

In my case, I use number conversion to add the rest of the office code to the outgoing station number, and then I use RONDI to add on the area code and form the complete 10 digit national number for the calling party.

Both the NU and RO settings (RONDI and RODDI for the dest codes pointed to the route) are tied to the LCR tables and the various entries made for dialled numbers.


> Besides, can you tell if I can make more routes with one >ISDN trunk, in which all lines are tied to the existing >rou?

You'll only have one "route"......you can however, have multiple ways to to manipulate and format dialled digit strings before they are actually sent out over that route to their destination.

>I'd like to create all routes, if neccesary, for >international, nat, unknown, and subscriber; could that be >possible with just one route per different destinations?

Essentially, yes........but it can get fairly complex (an unfortunate side effect of flexibility).

You first program the "route" - the physical trunks.(RODAI, ROCAI)

Then you assign destination codes which point to that "route". (RODDI)There is a parameterin that command - ADC - within which is determined the type of calling number, called number and other interrelated info.

The dest codes are then entered in LCR as the value for "PRE" in the Fictitious Destination Table (FDT).

Then entries are made in the various LCR tables for the dialled digits according to number length, possible conflict with other dialled numbers, digits to be added, digits to be removed - and possibly be replaced with other digits, dest code to be used before sending the call out to the trunks (which determines type of called and calling number)and formatting of the dialled number (TON).

If you didn't catch on, the dialled number is formatted in both the RODDI command and the LCDDI (LCR entry) command......the entries for both should agree with each other. Some CO switches are more forgiving than others when it comes to what the number is formatted as and the actual number sent.

For example, if I format an outbound number as "national", but send only xxx-xxxx instead of xxx-xxx-xxxx, my call may be rejected because a "national" (North American Numbering Plan)number is supposed to be 10 digits.

An AT&T 5E switch won't care, a Verizon GTD5 or a Seimens WILL care.


>Thank you again.


Good luck,

Dave Strang
 
dstrang1 or whosrdaddy;
Could you explain or help me with this.
Since I want to follow your guidances, I add new DEST (2) for National call-type, and delete the old one, DEST (0).
Then we cannot make the call any more, if we put it back, then the call is through. I know that we should leave it alone, but I want to know what else related to it prevents the new one to work?
Thanks again.
 
First rule: If it already works, don't change it!

Second, in order to try to determine why the 2nd one didn't work, you'll need to provide the printouts for RODDP:DEST=0;
and RODDP:DEST=2; to compare them.

C-ya,

Dave Strang
 
dstrang1 or whorsdaddy;
Could you look at the data I provide below to tell what's wrong, please.
I did everything you suggested and concentrated on TON=2 for national, the call is true, but the A-number did not show up correct, without the area code.

#### starting of data
<ROCAP:ROU=ALL;
ROUTE CATEGORY DATA

ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP

1 7110000000000010 5 0000000011 0 30 128 00151515 111100000031 001100

END

<RODAP:ROU=ALL;
ROUTE DATA

ROU TYPE VARC VARI VARO FILTER

1 SL60 H'00000300 H'10040000 H'00410000 NO

END

<RODDP:DEST=ALL;
EXTERNAL DESTINATION ROUTE DATA

DEST DRN ROU CHO CUST ADC TRC SRT NUMACK PRE

0 1 0225200000000250002001110 0 2 0
1 1 0125200000000250001001110 0 2 0
2 1 0025200000000250000001110 0 2 0
4 1 0425200000000250004001110 0 2 0

END

<RONDP:ROU=1;
ROUTE NUMBER DATA

ROU PRE ROUDIR EXNOPU EXNOPR TERAC

1 1-269
2-301
4-379

END

<ROELP;
PUBLIC EXCHANGE NUMBER PER LIM DATA

LIM EXNOPU

1 2-301

END

<NADAP;
NUMBER ANALYSIS DATA

TYPE OF SERIES NUMBER SERIES

EXTENSION NUMBER SERIES 1000 - 1999
3013

EXTERNAL DESTINATION CODE 0

LEAST COST ROUTING ACCESS
CODE NUMBER SERIES 7

TYPE OF SERVICE CODE SERVICE CODE

EXTERNAL NUMBER LENGTH DATA

EXTERNAL NUMBER NUMBER LENGTH

PROCEED TO SEND SIGNAL DATA

EXTERNAL NUMBER POS. TYPE

CALL DISCRIMINATION DATA

EXTERNAL/INTERNAL NUMBER CAT


END

<NUTRP:CNVTYP=0;
NUMBER CONVERSION DATA

ENTRY CNVTYP NUMTYP ROU TARDST PRE TRC NEWTYP CONT BCAP H
LC

269301379 0 1 9 0
301379 0 2 6 0
379 0 4 3 0
END

<NUTRP:CNVTYP=1;
NUMBER CONVERSION DATA

ENTRY CNVTYP NUMTYP ROU TARDST PRE TRC NEWTYP CONT BCAP H
LC

379 1 4 301 0
1 1 10 379 0
END

### end of data

If you need more information, let me know.
Thanks
 
hello everybody.
I restarted from no route; setup new one, new destination, new LCR code and table, new entries for number analysis; but just for TON=2 (national) as dstrang1, whosrdaddy, and ALEX recommend. However, the only thing that did not work right is the "sent A-number/connected number" option. I did as dstrang1 said, but cannot find out what went wrong. I have to cheat using the hardcode for area+office+extension.
We can live with it, but the company needs that feature to be dynamic. Can some body look at the data below and give me some help.

<NADAP;
NUMBER ANALYSIS DATA

TYPE OF SERIES NUMBER SERIES

EXTENSION NUMBER SERIES 1000 - 1999

EXTERNAL DESTINATION CODE 240

LEAST COST ROUTING ACCESS
CODE NUMBER SERIES 0

TYPE OF SERVICE CODE SERVICE CODE

EXTERNAL NUMBER LENGTH DATA

EXTERNAL NUMBER NUMBER LENGTH

PROCEED TO SEND SIGNAL DATA

EXTERNAL NUMBER POS. TYPE

CALL DISCRIMINATION DATA

EXTERNAL/INTERNAL NUMBER CAT


END


<ROCAP:ROU=ALL;
ROUTE CATEGORY DATA

ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP

1 7110000000000010 5 0000000011 0 30 128 00151515 111100000031 001100

END

<RODAP:ROU=ALL;
ROUTE DATA

ROU TYPE VARC VARI VARO FILTER

1 SL60 H'00000300 H'10040000 H'00410000 NO

END

<RODDP:DEST=ALL;
EXTERNAL DESTINATION ROUTE DATA

DEST DRN ROU CHO CUST ADC TRC SRT NUMACK PRE

240 1 0225200000000250002001111 0 4 0

END


<ROELP;
PUBLIC EXCHANGE NUMBER PER LIM DATA

LIM EXNOPU

1 1-269
2-301
4-379

END


<RONDP:ROU=1;
ROUTE NUMBER DATA

ROU PRE ROUDIR EXNOPU EXNOPR TERAC

1 1-269
2-301
4-379

END

<?LCDDP:TAB=DNT2;
LEAST COST DESTINATION DATA

NUMBER TABLE

ENTRY TRC PRE ACCT FRCT TOLL CBCS BTON TNS OSA

0240 1 0 1 111111111111111 0
END

<LCDDP:TAB=FDT;
LEAST COST DESTINATION DATA

FICTITIOUS DESTINATION TABLE

FRCT TZONE PRE

1 1 240
END


<NUTRP;
NUMBER CONVERSION DATA

ENTRY CNVTYP NUMTYP ROU TARDST PRE TRC NEWTYP CONT BCAP H
LC

301379 0 2 6 0
1 1 10 301379 0
END

<?<?KSCAP:DIR=ALL;
KEY SYSTEM CATEGORY PRINT

DIR TRAF SERV CDIV ROC ITYPE TRM ADC LANG BSEC

1001 00151515 0000100000 000000000 000001 33 0 00000000010000 F 0
1002 00151515 0000100000 000000000 000001 28 0 00000000010000 F 0

END

 
The BTON in the LCR entry, digit 2 in ADC for the dest code (type of called number) have to agree...in your case, you want to send the dialled number out as "National" so BTON=2 and bit 2 in ADC for the dest code also =2.

The RONDP/ROELP and NUTRP entries have to do with the *calling* number.

For the NUTRI entry, you have cnvtyp and numtyp = 1 and 10 respectively. The value for ENTRY = the internal directory number, and the value for PRE will = local office code associated with the DID number.
For ex: internal number = 1001 and the local public exchange number is 555-1001 (the complete National public number is 301-555-1001).

The number conversion entry would be: NUTRI:entry=1001,cnvtyp=1,numtyp=10,pre=555;

If you have digit #3 in ADC for the dest code set as "2" (type of calling public number = national)then your entry for RONDI is RONDI:ROU=1,EXNOPU=2-301;

Thus, when ext. 1001 initiates an external call, the number presented to the public network is 301-555-1001.

As for LCR entries for the dialled numbers......it appears above that you created an entry for the dest code - that's not necessary as dest codes are not actually *dialled*.
The dest code is dealt with in the FRCT parameter.

Aside from the ENT and FDT tables, your LCR entries deal with the numbers *exactly* as the user dials them, and how those digits are manipulated as they pass thru each table before they are actually sent to a particular trunk route.


FWIW, your LCR entry for FDT is correct.


Hope this helps,

Dave Strang
 
Dave, I changed all as you said, then make a call.
The public number is 379-1001. I am wondering if the 301 will be out on the trunk, since I am not sure if the "Tracer" software utility we have here collects data from inside PBS or at the "door" to the trunk
 
cspectra (TechnicalUser) 9 May 07 14:10 sed:

>Dave, I changed all as you said, then make a call.
>The public number is 379-1001. I am wondering if the 301 >will be out on the trunk, since I am not sure if >the "Tracer" software utility we have here collects data >from inside PBS or at the "door" to the trunk


Place a call to your cellphone or to an external number which you know can display caller ID.

Good luck,

Dave Strang
 
Dave;
I did many times. The number appear on the MS phone is 301-379-1000 which is the CLIP numbet that the provider set-up at their side. If I hardcode the PRE, then the EXT numbbers show correctly.
Is there any other things that might prevent this? I can provide more data. Thanks

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top