External Foll.me doesn't wok for some numbers for same extension

[cuneyt2020]

Hi , shortly the problem is this:
Extension 4061 can call the numbers 005321234567 and 00216 1234567 (This is md110 bc10 cn144)

When i try *22# "enter ecf number" 00216 1234567# , it's ok
But when i try *22# "enter ecf number" 005321234567# on DTS screen it says "procedure failed"

These two destinations 00216 and 00532 goes to same routes which is connected to another md110 pbx.. But on the other md side, these two destinations, they go to different routes..

dest 00532 -- route55 problem
\ /
BC10 side ----route98--- md110 bc9 side
/ \
dest 00216 route 1 ok





Is there any parameter for routes that restircts the external follow-me? Or any other suggestions?
Rgrds

 

[whosrdaddy]

check the adc's of both dests

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[cuneyt2020]

Well you're right daddy, when i change the ADC parameter to the right one it's ok for external follow me, but i will try to find which adc parameter is related with it. And it's really hardwork to do because it's a production system and i can not try it by removing the destination and creating it with the new ADC parameter

Thx for your help

 

[whosrdaddy]

give these printouts :

RODDPEST=00532;
RODDPEST=00216;

reprogramming a dest is a matter of seconds (via batchfile), even on a production system

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[cuneyt2020]

<rODDP:dest=0053&00216;


Hi daddy
this is the old config if it's possible i want to change ADC of 0053 with the correct one( only changing the related parameter. The critical point is i have alternative route for dest 0053 and the alternative route is in another MD110 pbx. I mean, these two choices for 0053 dest is, going to different md110 pbxes and adc parameter should be configured for a right switching mechanism when the other choice is out of order.
That's why it's hardwork for me to test it.
[tt]

EXTERNAL DESTINATION ROUTE DATA
DEST DRN ROU CHO CUST ADC TRC SRT NUMACK PRE
0053 98 0606100000000250006 1 1 0 8218
92 1 0606100000000250006 1 1 0 07
00216 98 2005000000000250000 5 1 0 8217
92 1 0606100000000250006 1 1 0 07


[/tt]

 

[cuneyt2020]

Another note is, when i changed the ADC parameters of dest 0053 same as the 00216's ADC parameters, seen on above, alternative choice didn't work.

 

[whosrdaddy]

I mean, these two choices for 0053 dest is, going to different md110 pbxes and adc parameter should be configured for a right switching mechanism when the other choice is out of order.
That's why it's hardwork for me to test it.

just program a new destination with only the overflow route (92) to do the testing?

one small question though,

concerning the overflow problem
are the PRE's configured in NADAP? let me explain :

suppose we have a dest 0 for outgoing calls, and for some reason I want to put digits in front of my dailed number (for carrier select usage) :

so :

RODDIEST=0,ROU=X,ADC=0005000000000250000,trc=1;

now i can call 00033xxx to france, 0033xxx is sent to the network.
lets add a carrier select code (assume it is 1234) :

RODDEEST=0;
RODDIEST=0,ROU=X,ADC=0005000000000250000,trc=1,PRE=1234;

however, this wont work, because when adding a prefix, your number is reanalyzed. so if 1234 is not in ED you'll get NU tone.

a common practice is to readd the original prefix to prevent errors of this type :

RODDIEST=0,ROU=X,ADC=0005000000000250000,trc=1,PRE=01234,srt=2;

this is what happens :

i call 00033xxx :

first 0 gets truncated (TRC = 1), so we have 0033xxx
we add 01234 prefix = 012340033xxx
and start sending from the second digit (SRT=2)
so 12340033xxx is sent to the network

concerning your ext follow me problem :

in dest 0053, you set the called party number type (D2&D19 of ADC) to 6, which is a local private number. this means that this wont be an EXTERNAL follow me (public network) but an INTERNAL follow me (private newtork) so setting D2&D19 to 0 (unknown public nr) will do the trick
digit D5 should be 0 to avoid sending supplementary services because the receiver may not be a MD110 pbx

hope this makes sense,
Daddy

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[cuneyt2020]

Hi daddy, First of all your advice is ok and now external follow me is ok for dest 0053 by changing d2 and d19
But my first problem is different then you mentioned.
Let me explain...
Telecom A
|
dest 00532 route55 PRI
\ /
BC10 side ----route98--- md110 bc9 side
/
/route92
/
BC12 side
|
| Route50 analog trunk
|
Telecom B



For dest 0053 there are two choices one of them uses Telecom A and other choice uses Telecom B When there is a problem in Telecom A (route 55 is blocked) due to ADC parameter it may not switch to telecom B side...This is our another problem regardless of this topic.. For example, i tried with the ADC parameters same as 00216 , but it didn't switch to telecom B

As a result i mean that if there is an md110 network and if you use telecom routes of these different routes, working alternative choice of the routes depend on ADC parameters..
But it's ok now by changing ony the d2 and d19 digits. I tested the alternative choice by blocking route 55 and it's ok with this ADC parameters. Thx again.
Rgrds.

 

[whosrdaddy]

ok,

glad I could help

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!