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!

nutri to dest

Status
Not open for further replies.

cuneyt2020

Technical User
Mar 9, 2004
147
TR
Hi, we want to set a number conversion to route, so that the converted number will be a dest and the customer will call outside by the help of this dest number. The problem is, when the number is converted to an extension , it works properly, but when the same number is converted to dest number it doesn't work?
What should be the reason..
Md version is bC12 SP6

Route parameter, destination parameter and nutrp which doesn't work, is like this,

[tt]
<rodap:rou=68;
ROUTE DATA
ROU TYPE VARC VARI VARO FILTER
68 SL60 H'00000300 H'00000000 H'04310000 NO

END

<rocap:rou=68;
ROUTE CATEGORY DATA
ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
68 0110000000000010 4 2000030001 0 30 128 00151515 111110000031 001100

<roddp:DEST=all;
EXTERNAL DESTINATION ROUTE DATA
DEST DRN ROU CHO CUST ADC TRC SRT NUMACK PRE
0100 55 2005000000000250000000000 0 3 0
01021 98 1606100000000250006000000 0 1 0
7 1 2005000000000250000000000 0 3 0
7 2 2005000000000250000000000 0 3 0
01022 7 2005000000000250000000000 0 3 0
01023 92 1606100000000250006000000 0 1 0
7 1 2005000000000250000000000 0 3 0
7 2 2005000000000250000000000 0 3 0
01024 92 1606100000000250006000000 0 1 0
7 1 2005000000000250000000000 0 3 0
01025 7 2005000000000250000000000 0 3 0
01026 7 2005000000000250000000000 0 3 0
01027 7 2005000000000250000000000 0 3 0
01028 7 2005000000000250000000000 0 3 0
01029 7 2005000000000250000000000 0 3 0
01031 92 1606100000000250006000000 0 1 0
7 1 2005000000000250000000000 0 3 0
7 2 2005000000000250000000000 0 3 0
01032 7 2005000000000250000000000 0 3 0
01033 7 2005000000000250000000000 0 3 0
01034 7 2005000000000250000000000 0 3 0
01035 7 2005000000000250000000000 0 3 0
01036 7 2005000000000250000000000 0 3 0
01037 7 2005000000000250000000000 0 3 0
01038 7 2005000000000250000000000 0 3 0
01039 7 2005000000000250000000000 0 3 0 nutrp; (rou=68 is the related one)
NUMBER CONVERSION DATA
ENTRY CNVTYP NUMTYP ROU TARDST PRE TRC NEWTYP CONT BCAP HLC
0100 0 0 08 2 0
2242 0 0 0001 4 0
5446 0 0 5353 4 0
7000 0 0 8403 0
7900 0 0 0000 4 0
1021 0 0 68 01 4 0


[/tt]

when i make the nutri

nutri:ROU=68,ENTRY=1021,CNVTYP=0,NUMTYP=0,PRE=5621,TRC=4;

5621 is an extension, and the nutri works properly..

Any idea to advise me? I tried other numtypes and nothing changed...
Rgrds



 
if I'm reading this correct you want forward a
call coming from rou 68 towards public?

so 1021 incoming from rou 68 should take dest 01021?
then nutri should be :

nutri:ROU=68,ENTRY=1021,CNVTYP=0,NUMTYP=0,PRE=0,TRC=0;



--------------------------------------
What You See Is What You Get
 
Hi whosrdaddy,

What i want to do is, when digits come from route 68 (i.e 1021 02164444444, i want to convert it to 01 02164444444) when digits come such as 1021 03124444444 , i want to convert it to 0103124444444
so 1021 should be converted to 01

And i gave the command nutri:ROU=68,ENTRY=1021,CNVTYP=0,NUMTYP=0,PRE=01,TRC=4;

But when i try to convert it to a digits such as 01, which is a prefix for different routes,it is useless.When i test it, It gives tri-tone

if 1021 had been converted to a fixed extension (an ODN number for exp.) it should have been no problem. md accepts it and it dials the ODN


The dest.numbers 01021 01031 .. etc are working properly..No problem on dest number if no conversion had been done before.

Thanks for the reponse
 
ok now I understand your problem.

looking into your MD110 programmation, this should work.
a few questions though, if you dial the dest manually (like 01031...), does it work??
you can always do a call trace to understand what happens

/* setup trace, x = lim trunks from rou 68 stuni:unit=slp60,lim=x,msksig=02&03&A1,store=yes;
/* set size
sttss:tri=1,size=500;
/* start trace
sttsi:tri=1;
/* make call
/* stop trace
sttse:tri=1;
/* print trace
strap:tri=1;

if you dont have a signal interpreter, paste trace results here, we will do it for you.
these prints are also useful :

ROEDP:ROU=ALL,TRU=ALL;
NADAP;

greetings,
Daddy

--------------------------------------
What You See Is What You Get
 
Hi to all
Whosrdaddy is a magician
But I have some questions for Daddy.

Q:1
ADC for route with DEST 01021 01031 are set as local private number (6 on position D2 and D4 in ADC) and nutrX ( X represent last letter ) NUMTYP is always is set as Unknown public number.
Why and in my opinion it can be a problem.
Q:2 I think that printout of command RONDP:ROU=68 is needed
Q:3 the length of sending digits using roddX
NUTRX cut 4 digits and add 2 digits

What You think about?

Sorry my English is no perfect

 
Q1 : you must specify numtyp for INCOMING call, it doesn't depend where you send the call to, but you're correct in asking this question, that's why I requested a call trace...
Q2 : wrong, rondp is for outgoing calls, not for incoming calls
Q3 : ?? what do you mean ??

cheers

--------------------------------------
What You See Is What You Get
 
Hi
Are you sure that route support private TON ?
Try with D19 in ADC set to "0
 
Hi all,
I checked the TLU trace and saw that it's not MD's fault...
Last two digits were missing (our gateway's sending less digits. There is a limitation i think)
I sent 1021 0256 4440333 via route 68 to md110 and saw on trace that the digits are 1021 025644403

When i made the conversion with 09, it worked properly
So no problem now...

thanks for your help

Rgrds.


part of trace
18.31.03.960
-> Outgoing
Call Reference: #094
Message: CALL PROCEEDING

18.31.04.620
-> Outgoing
Call Reference: #094
Message: ALERTING
Progress Indicator
Coding Standard: CCITT standardized coding
Location: Private network serving the local user
Progress Description: In-band information is now available

18.31.06.280
<- Incoming
Call Reference: #096
Message: SETUP
Bearer Capability
Coding Standard: CCITT
Information transfer capability: 3.1 kHz audio
Transfer mode: Circuit mode
Information transfer rate: 64 kbit/s
User information layer 1 protocol: CCITT G.711 A-Law
B-Channel: 29
Progress Indicator
Coding Standard: CCITT standardized coding
Location: Private network serving the local user
Progress Description: Origination address is non ISDN
Calling Party Number
Type of number: Unknown
Numbering plan: Unknown
Presentation indicator: Presentation restricted
Screening indicator: User-provided, verified and passed
Digits: 059992
Called Party Number
Type of number: Unknown
Numbering plan: ISDN/telephony numbering plan
Digits: 1021025644403
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top