roddi question 3

[pawshman]

hi guys yet another one from the banks of roddi land !

briefly, a customer dials
62700

the provider needs to see
1667742700

Theres a lot of different ranges and provider scenario so without getting into a song and dance, have tried this, pls check me ?

SO,
EX-DEST= 627

RODDIEST=627,TRC=1,PRE=166774,SRT=1

THIS then sends out to line

1667742700 ?

cheers

 

[dstrang1]

pawshman (Programmer) 18 May 05 10:45 sed:
>hi guys yet another one from the banks of roddi land !

I believe you'll have better luck if you do it this way:

RODDIEST=627,TRC=3,PRE=627166774,SRT=4;


C-ya,
Dave Strang

 

[whosrdaddy]

small explanation to pawshman :

the reason why your roddi won't work is very simple.
if you use the PRE parameter in RODDI, the new formed number (166774xxx) will go through number analysis again, chances are great that 1 or 16 or 166 or 1667 (and so on) is not defined as ED in NADAP. that's why dave's RODDI will work since the new formed number will be 627166774, and 627 is known as ED in NADAP. life can be simple...

--------------------------------------
What You See Is What You Get

 

[pawshman]

HI Fellas, (and thanksx)

ok still got a problem. I did the RODDI has suggested.

I have 3 scenarios (and signal traces and programming.)

FAIL SCENARIO 1: USER DIALS 6 5365
should send to line 1667745365

PHONE: says calling then message "the number you've dialled has not been recognised"

signal trace shows 16677453 going out as an SSRM(i)
see below

-----------------------------------------------------------
FILTERS APPLIED - (FILE/OPTIONS menu)
Direction: Show send and receive messages
Message type: Show real and virtual messages
LAP/SQU Number: Show all LAP/SQU messages

10.21.52.500 00108 SEND REAL 2-3-00/LAP = 11 Only SIGNAL
01 10
Message----------------{ ISRM(I), Initial Service Request Message (Incomplete)
Service Indicator (10)-{ Speech, 64kbit/s PCM or Analogue
Selection Field--------{

10.21.52.640 00153 SEND REAL 2-3-00/LAP = 11 Only SIGNAL
0B 31 36 36 37 37 34 35 33
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 16677453

10.21.57.340 00154 RECEIVE REAL 2-3-00/LAP = 11 Only SIGNAL
09
Message----------------{ NAM, Number Acknowledge Message
Selection Field--------{

--- End of file. --------------------------------

FAIL SCENARIO 2: USER DIALS 71 16677 4 5365
PHONE: SAME AS ABOVE MESSAGE
71 IS ACCESS CODE

TRACE SHOWS "ALL" DIGITS GOING OUT AS SSRM(I)
SEE BELOW

-----------------------------------------------------------
FILTERS APPLIED - (FILE/OPTIONS menu)
Direction: Show send and receive messages
Message type: Show real and virtual messages
LAP/SQU Number: Show all LAP/SQU messages

10.34.08.100 00082 SEND REAL 2-3-00/LAP = 24 Only SIGNAL
01 10
Message----------------{ ISRM(I), Initial Service Request Message (Incomplete)
Service Indicator (10)-{ Speech, 64kbit/s PCM or Analogue
Selection Field--------{

10.34.09.000 00152 SEND REAL 2-3-00/LAP = 24 Only SIGNAL
0B 31
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 1

10.34.09.440 00166 SEND REAL 2-3-00/LAP = 24 Only SIGNAL
0B 36
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 6

10.34.09.620 00170 SEND REAL 2-3-00/LAP = 24 Only SIGNAL
0B 36
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 6

10.34.10.360 00174 SEND REAL 2-3-00/LAP = 24 Only SIGNAL
0B 37
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 7

10.34.10.500 00178 SEND REAL 2-3-00/LAP = 24 Only SIGNAL
0B 37
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 7

10.34.11.240 00182 SEND REAL 2-3-00/LAP = 24 Only SIGNAL
0B 34
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 4

10.34.11.660 00186 SEND REAL 2-3-00/LAP = 24 Only SIGNAL
0B 35
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 5

10.34.11.840 00190 SEND REAL 2-3-00/LAP = 24 Only SIGNAL
0B 33
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 3

10.34.12.020 00198 SEND REAL 2-3-00/LAP = 24 Only SIGNAL
0B 36
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 6

10.34.12.160 00203 SEND REAL 2-3-00/LAP = 24 Only SIGNAL
0B 35
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 5

10.34.12.700 00204 RECEIVE REAL 2-3-00/LAP = 24 Only SIGNAL
09
Message----------------{ NAM, Number Acknowledge Message
Selection Field--------{

--- End of file. --------------------------------

PASS SCENARIO 3: they can dial mobiles over this same network by dialling 9 and the mob number, (ive edited the trace to mask my mobile number, so they dial
9 07980 123456, trace shows SSRM(c) this works

so sends to line 16677 07980 123456

see below

FILTERS APPLIED - (FILE/OPTIONS menu)
Direction: Show send and receive messages
Message type: Show real and virtual messages
LAP/SQU Number: Show all LAP/SQU messages

10.45.38.520 00169 SEND REAL 2-3-00/LAP = 18 Only SIGNAL
01 10
Message----------------{ ISRM(I), Initial Service Request Message (Incomplete)
Service Indicator (10)-{ Speech, 64kbit/s PCM or Analogue
Selection Field--------{

10.45.38.640 00223 SEND REAL 2-3-00/LAP = 18 Only SIGNAL
0B 31 36 36 37 37 30 37 39 38 30
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 1667707980

10.45.39.180 00239 SEND REAL 2-3-00/LAP = 18 Only SIGNAL
0B 37
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 1

10.45.39.400 00243 SEND REAL 2-3-00/LAP = 18 Only SIGNAL
0B 35
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 2

10.45.39.660 00247 SEND REAL 2-3-00/LAP = 18 Only SIGNAL
0B 30
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 3

10.45.39.920 00251 SEND REAL 2-3-00/LAP = 18 Only SIGNAL
0B 37
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 4

10.45.40.100 00259 SEND REAL 2-3-00/LAP = 18 Only SIGNAL
0B 38
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 5

10.45.40.340 00264 SEND REAL 2-3-00/LAP = 18 Only SIGNAL
0C 37
Message----------------{ SSRM(C), Subsequent Service Request Message (Complete)
Selection Field--------{ 6

10.45.45.100 00265 RECEIVE REAL 2-3-00/LAP = 18 Only SIGNAL
09
Message----------------{ NAM, Number Acknowledge Message
Selection Field--------{

10.45.49.180 00337 RECEIVE REAL 2-3-00/LAP = 18 Only SIGNAL
05
Message----------------{ CCM, Call Connected Message
Selection Field--------{

--- End of file. --------------------------------

so problem !

when you dial 71, you are bypassing the LCR this fails, so I think its provider. Have attached some prinouts

<NADAP;
NUMBER ANALYSIS DATA
TYPE OF SERIES NUMBER SERIES
EXTERNAL DESTINATION CODE 2771 - 2778
630 - 639
LEAST COST ROUTING ACCESS
CODE NUMBER SERIES 9
EXTERNAL NUMBER LENGTH DATA
EXTERNAL NUMBER NUMBER LENGTH
2778 4 - 20
6 5 - 5
PROCEED TO SEND SIGNAL DATA
EXTERNAL NUMBER POS. TYPE
CALL DISCRIMINATION DATA
EXTERNAL/INTERNAL NUMBER CAT
6 3 2 1 0

BREAK DURING PRINTOUT

<LCDDP:TAB=DNT1;
LEAST COST DESTINATION DATA
EXCEPTIONS TABLE
ENTRY TRC PRE ACCT FRCT TOLL CBCS BTON TNS OSA
907980 1 0 16 111111111111111 0

<LCDDP:TAB=FDT;
LEAST COST DESTINATION DATA
FICTITIOUS DESTINATION TABLE
FRCT TZONE PRE
16 1 2778
END

<RODDPEST=2778;
EXTERNAL DESTINATION ROUTE DATA
DEST DRN ROU CHO CUST ADC TRC SRT NUMACK PRE
2778 2 0605000000000250000 4 5 0 277816677
6 1 0605000000000250000 4 5 0 277816677
1 2 0605000000000250000 4 5 0 277816677
10 1 0605000000000250000 4 5 0 277816677
1 1 1 0605000000000250000 4 5 0 277816677

END

<RODDPEST=653;
EXTERNAL DESTINATION ROUTE DATA
DEST DRN ROU CHO CUST ADC TRC SRT NUMACK PRE
653 2 0005000000000250000 3 4 0 65316677453

END

<ROCAP:ROU=2;
ROUTE CATEGORY DATA
ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
2 013000000000001 5 2100030000 0 15 128 00151510 111100000020 111111

END

<RODAP:ROU=2;
ROUTE DATA
ROU TYPE VARC VARI VARO FILTER
2 TL50 H'0000000C H'00000000 H'00000000 NO

END

 

[PCLOP]

You got wrong DEST

dial:62700
sent out:1667742700

This is right:RODDIEST=627,TRC=1,PRE=627166774,SRT=4;


this is wrong:RODDIEST=627,TRC=3,PRE=627166774,SRT=4;

 

[pawshman]

pclop,
I tried as you suggested, user gets number unobtainable.

the dest "is" 653, I'm assuming you said 62700 as an example
as user needs to dial 6 5365 !

I've contacted the provider, as I want to know why when you manually select a trunk it does not work.

still any ideas on the signal traces ??????

 

[dstrang1]

hi guys yet another one from the banks of roddi land !

briefly, a customer dials
62700

the provider needs to see
1667742700

Theres a lot of different ranges and provider scenario so >without getting into a song and dance, have tried this, >pls check me ?

>SO,
>EX-DEST= 627

>RODDIEST=627,TRC=1,PRE=166774,SRT=1

>THIS then sends out to line

>1667742700 ?


No.....


RODDIEST=627,TRC=3,PRE=6271667742700,SRT=4;

Original dest code is truncated, and replaced by prefix of original dest AND additional digits that need to be sent, SRT states that actual digit transmission upon line seizure will begin with the 4th digit.

Then you said"
>FAIL SCENARIO 1: USER DIALS 6 5365
>should send to line 1667745365

Is "6" an LCR access?

If so, and is 5365 part of a number range that acually begins with 166774 on the network to which you're placing the call?

What you need to do is set up the DNT1 entry for 65365 (or whatever is the simplest form of the intended number range)for TRC=1, which strips off the "6", PRE=166774...the digit string then beomes 1667745365.
The FRCT value should be for dest code set for the intended route that has ADC set to agree with necessary criteria for the type of trunks and SRT set to one digit longer than the dest code (if dest is 3digits, then SRT=4).

The BTON in the LCDDI entry and in ADC for the dest code should also agree. Some switches are more forgiving than others when it comes to number formatting and silly stuff like that can have you troubleshooting around in circles.



>PHONE: says calling then message "the number you've >dialled has not been recognised"

>signal trace shows 16677453 going out as an SSRM(i)
>see below

You're not sending the last 2 digits.....

Then you sed:
>the dest "is" 653, I'm assuming you said 62700 as an >example
>as user needs to dial 6 5365 !

You used 62700 in your first post.....I guess the exact call case is unclear.

Are you using LCR or are users dialling dest codes which you're trying to translate into another number?

Can you give a more accurate example of the true dialling scenario as it is from a user dialling perspective?

Thanks,

Dave Strang









cheers

 

[pawshman]

Hi Dave,

cheers for the reply have been busy...

arrrgh users.

ok I've manged to confirm some things, the scenario was given to me slighly inaccurate.

Have tested on site (the orginal extension was not in the number providers number range)

------------------------------------------------------------

so MANUALLY from site the below works

9 16677 5 65249

so to explain

9= sieze an outside line
16677= is access code for the providers least cost routing
5= the provider is expecting FIVE digits
65249= is the desk number to mobile

so I have to get the MD to do send out to line

16677565249 when the user dials 65249

652 is an ED in the nadap
652 is also a RODDI

cheers, nearly there...
my brain hurts need beer

 

[pawshman]

RIGHT------------------------------------------------------

What I have tried (all 3 have failed)

1)RODDIEST=652,TRC=3,SRT=4,PRE=652166775
also
2)RODDIEST=652,TRC=1,SRT=4,PRE=652166775
also tried
3) DNT1=ENTRY=652,TRC=1,FRCT=17
FDT= FRCT=17,PRE=652
RODDIEST=652,TRC=4,SRT=5,PRE=652166775

in the first example the below signal trace shows 166775 going out but not the rest of the digits.

as a reminder it is a number range
so customer will dial 652xx
so here cust dials 65249
provider needs to see 166775652xx

signal trace as follows:

***** SA-DPNSS decode of - C:\Documents and
DECODE MADE: Tue May 24 11:30:03 2005
FILTERS APPLIED - (FILE/OPTIONS menu)
Direction: Show send and receive messages
Message type: Show real and virtual messages
LAP/SQU Number: Show all LAP/SQU messages

11.24.46.460 00106 SEND REAL 2-3-00/LAP = 09 Only SIGNAL
01 10
Message----------------{ ISRM(I), Initial Service Request Message (Incomplete)
Service Indicator (10)-{ Speech, 64kbit/s PCM or Analogue
Selection Field--------{

11.24.46.580 00142 SEND REAL 2-3-00/LAP = 09 Only SIGNAL
0B 31 36 36 37 37 35
Message----------------{ SSRM(I), Subsequent Service Request Message (Incomplete)
Selection Field--------{ 166775

11.24.51.660 00143 RECEIVE REAL 2-3-00/LAP = 09 Only SIGNAL
09
Message----------------{ NAM, Number Acknowledge Message
Selection Field--------{

--- End of file. ---

 

[whosrdaddy]

the first RODDI must work, but it seems you have a numberlength problem, check NADAP:NUMTYP=NL; for 6 or 65 or 652,... entries, adjust them or delete them...

--------------------------------------
What You See Is What You Get

 

[pawshman]

RE: NUMBER 3)
that was wrong tried,

dnt1 entry=652,pre=166775,trc=0,frct=17
frct 17 pre=2774
roddi:dest=2774,pre=2774,TRC=4,SRT=1

still no joy,
time for some beer

 

[whosrdaddy]

ow see what you did wrong,

your roddi must be

RODDIEST=652,TRC=0,SRT=4,PRE=652166775,...

in fact this is the execution order for RODDI

TRC
PRE
SRT

your roddi was
RODDIEST=652,TRC=3,SRT=4,PRE=652166775,...

applying this to a call to 65249

you'll get 16677549 as result

for LCR do this :

nansi:numse=652,numtyp=LC; //you need to put 652 into LC or else it won't be parsed into LCR
nansi:numse=19,numtyp=ED; (choose appropriate ED, 19 is an example here)
tables :
DNT1= ENTRY=652,TRC=3,FRCT=17
FDT= FRCT=17,PRE=19
RODDIEST=19,TRC=2,SRT=3,PRE=19166775652

Cheers


--------------------------------------
What You See Is What You Get

 

[dstrang1]

pawshman (Programmer) 24 May 05 7:23 wrote:




>RE: NUMBER 3)
>that was wrong tried,

>dnt1 entry=652,pre=166775,trc=0,frct=17
>frct 17 pre=2774
>roddi:dest=2774,pre=2774,TRC=4,SRT=1

>still no joy,
>time for some beer

You're killin' yourself here......it looks to me like you're trying to manipulate the digits in both LCR and with the dest code

>so MANUALLY from site the below works

>9 16677 5 65249

>so to explain

>9= sieze an outside line

Is this (9) an LCR access or dest code?

>65249= is the desk number to mobile

Is this number part of a contiguous number range -- like 652XX or 65100 thru 65499 or something?




>16677= is access code for the providers least cost routing

>5= the provider is expecting FIVE digits

I'm lost on this one......you actually have to send a digit to the other end to let it know how many more digits you're sending?? Or do you just need to send the digit "5"?

>so I have to get the MD to do send out to line

>16677565249 when the user dials 65249

OK, if 652 is the actual dest code, I'm going to assume that 652XX is the number range for the far end (either that or you're going to have a boatload of dest codes). And I'm going to assume that you know what the ADC values for this route are in order to function correctly if the correct digits are sent......

User dials 652XX -- RODDI should be Roddi:dest=652,trc=3,pre=652166775,srt=4,adc=whatever is correct for your trunks;

Digits sent when user dials 65249 will be 16677565249.

This is for users dialling dest codes, and nothing is sent thru LCR.

If user needs to dial "9-652XX" with 9 being an LCR access,

then the DNT1 entry would be: LCDDI:TAB=DNT1,ENTRY=9652,TRC=4,PRE=166775652,FRCT=DIFFERENT DEST CODE FOR SAME ROUTE AS USED FOR DEST CODE 652 IN EXAMPLE ABOVE.

In other words, you assign a new dest code pointed at the same route with dest=xxx, trc=0,srt=4 (if 3 digit dest code)and the ADC with the correct values for the route.

Then you assign the new dest code to an FRCT value in fdt -- the new FRCT value is wha you put in FRCT for the LCDDI entry above.

If you send the DNT1 entry to the FRCT value corresponding with dest code 652, then you will be sending 166775652166775652XX.

I just set this all up and tested on my system -- I have a 3lim system @BC12sp6 w/DPNSS tie to a 61LIM system on BC9, with PRI to local telco.

I set up a dest code that I dial along with the last 2 digits of my cell phone number...

<RODDIEST=2513,ROU=69,ADC=1426100000000250004001100,SRT=5,TRC=4,PRE=2513970788;

When I dial 251310.....my cell phone rings.

2513 is the dest code, I strip that off (TRC=4) and reinsert it along with 9-707-88......9 is the LCR access out of the 2nd MD, with 707-88 being the exchange and 1st 2 digits of my cell. SRT=5 means that the 1st 4 digits of the prefixed digit string are not sent.

You can accomplish what you're trying either with dialling a dest code OR thru LCR -- you can even use both, but you have to use a different dest code for each method.

Good luck,

Dave Strang

 

[pawshman]

hey HEY HEY !

Many thankxs guys, cracked it

2 things

1) the number length was set at 5/5 set to 4/20
(that def. causes a problem)

and trc=0 and srt=4 worked

thankxs for the explanation on the LCR, after that bit it clicked.

its the ORDER that was not making sense

cheers again

gold stars all round

and you can all go home early

PM