A Number Display

[alchohaz]

I have now sucessfully set up IP routes between sites as a trial (Hurrah). However before i start to implement LCR to deliver DDI calls over these links as choice 1, I need to make sure that the distant ends get something intelligable on their displays, for example if i call Rotterdam from London, i need the people at Rotterdam to have a bit more on their display than my 4 digit extension number. Ideally i woud like them to see a site code of some sort site ID number or even better a full DDI number.

I have tried various options with the NUTRI at both ends of the link but so far have no joy... (The A end would be the better solution for NURTI comand - Local Exchange)

Any ideas?




[red]Striker : My orders came through. My squadron ships out tomorrow, we're bombing the storage depots at Daiquiri at 18:00 hours. We're coming in from the North, below their radar.[/red]
[blue]Elaine : When will you be back?[/blue]
[red]Striker : I can't tell you that? It's classified.[/red]

 

[rfpui]

Did You tried RONDI;?

----------------------------------
If anything can go wrong, it will.
(Murphy's Law)

 

[alchohaz]

Nope, never used it before. Can it be used at the "a" party exchange? This is because the route at the distant exchange will have calls coming in from more than one source, i.e. call will NOT only be from London so a prefix of 020xxx will not be applicable in all cases.

I will look into RONDI but any further tips appreciated.

Cheers
Al








[red]Striker : My orders came through. My squadron ships out tomorrow, we're bombing the storage depots at Daiquiri at 18:00 hours. We're coming in from the North, below their radar.[/red]
[blue]Elaine : When will you be back?[/blue]
[red]Striker : I can't tell you that? It's classified.[/red]

 

[rfpui]

... Can it be used at the "a" party exchange?...
Only at the A.

can You send to forum
RODDPEST=..;"London"?
To correct set RONNDI, type of number must be this same!!!!

----------------------------------
If anything can go wrong, it will.
(Murphy's Law)

 

[alchohaz]

<roddp:dest=75aaa;EXTERNAL DESTINATION ROUTE DATA
DEST  DRN ROU CHO CUST ADC                        TRC SRT NUMACK PRE
75aaa     BB           0626100000000050006000000  5   6   0      75aaa          

END
 
<roddp:dest=75060,ipopt=yes;EXTERNAL DESTINATION ROUTE DATA
DEST  DRN ROU CHO CUST IP ADDRESS       RROUID         
75aaa     BB           00.00.00.00      RTDM

[red]Striker : My orders came through. My squadron ships out tomorrow, we're bombing the storage depots at Daiquiri at 18:00 hours. We're coming in from the North, below their radar.[/red]
[blue]Elaine : When will you be back?[/blue]
[red]Striker : I can't tell you that? It's classified.[/red]

 

[rfpui]

Try in Rotterdam
RONDI:ROU=BB,EXNOPR=6-020;

and make call from Rotterdam to London;


----------------------------------
If anything can go wrong, it will.
(Murphy's Law)

 

[alchohaz]

RFPUI - thanks for your help, i have made a bit of progress with:

<nutrp;
NUMBER CONVERSION DATA
ENTRY                CNVTYP NUMTYP ROU      TARDST  PRE                  TRC NEWTYP CONT BCAP HLC
       
1                    2      2      60               00044207xxx                     0        
2                    2      2      60               00044207xxx                     0        
END

BUT this will cause me an issue later on if a number with extension starting 1 or 2 arrives from another site on route 60.

For example if the call were to originate from Bristol, then the "pre" would need to be different. Do you follow me?

Really i need to get this (equivalent) set in the NUTRI at the originating site.. seems a bit "funny" this programming did NOT work earlier !!










[red]Striker : My orders came through. My squadron ships out tomorrow, we're bombing the storage depots at Daiquiri at 18:00 hours. We're coming in from the North, below their radar.[/red]
[blue]Elaine : When will you be back?[/blue]
[red]Striker : I can't tell you that? It's classified.[/red]

 

[rfpui]

Hi
You wont "change" incoming number

But I think that solution is to change sending number.

If You make call from London to Rotterdam or Bristol are you use this same ROute?


----------------------------------
If anything can go wrong, it will.
(Murphy's Law)

 

[whosrdaddy]

alchohaz,

you just need to work with exchange numbers. for example, let's give rotterdam EN 940 and london EN 941

so if a user in rotterdam wants to reach london, they would do 940 + extension nr

rotterdam config

nansi:numse=941,numtyp=en;
roddi:dest=940,rou=x,adc=0626100000000050006000000,srt=1;
rondi:rou=x,exnopr=6-941;
syidi:exgid=941;

london config
nansi:numse=940,numtyp=en;
roddi:dest=941,rou=y,adc=0626100000000050006000000,srt=1;
rondi:rou=y,exnopr=6-940;
syidi:exgid=940;

for the transit calls, you must have licencse for original A-number and set ADC digit D22 to 1

your nutri trick will only work if D24=1 (enhanced sent A-Number conversion)


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

 

[alchohaz]

Still not getting anything across the link, into i hope to have this work with name identity across the link.. is this feasible?

Here's the current set i am using:

LICENCE TAG                              FAL          ALLOWED
ACD-AGENT                                FAL104525         16
ANALOGUE-EXTENSION                       FAL104451        400
ANCD-V24-INTERFACE                       FAL104526          0
APP-LINK-INTERFACE                       FAL104536          0
BASE-STATION-DECT                        FAL104520          0
CAS-EXTENSION                            FAL104455          0
CCM-ETH-INTERFACE                        FAL104531          0
CCM-V24-INTERFACE                        FAL104530          0
CIL-HDU-INTERFACE                        FAL104710          0
CORDLESS-EXTENSION                       FAL104454          0
CTT-EXTENSION                            FAL104457          0
DIGITAL-EXTENSION                        FAL104452       1052
DTMF-RECEIVER-MOB-EXT                    FAL1043610         0
DUPLICATED-CS                            FAL104491          0
EM-ETH-INTERFACE                         FAL104538          0
EM-V24-INTERFACE                         FAL104537          0
EXTERNAL-LINE-APNSS                      FAL104467          0
EXTERNAL-LINE-CAS-ANA                    FAL104461          0
EXTERNAL-LINE-CAS-DIG                    FAL104462          0
EXTERNAL-LINE-CCSS7                      FAL104705          0
EXTERNAL-LINE-DASS                       FAL104463        210
EXTERNAL-LINE-DPNSS                      FAL104465         60
EXTERNAL-LINE-H323                       FAL1042179         8
EXTERNAL-LINE-H323-SERV                  FAL1043611         0
EXTERNAL-LINE-ISDN-NET                   FAL104507         30
EXTERNAL-LINE-ISDN-USR                   FAL104464          0
EXTERNAL-LINE-QSIG                       FAL104466          0
FIXED-REMOTE-EXTENSION                   FAL1040524         0
FREESEATING                              FAL1040050     65535
GENERIC-EXT-SMS                          FAL104708      65535
GROUP-SWITCH-LINK                        FAL104492         14
IP-EXTENSION                             FAL104706          0
IS-ETH-INTERFACE                         FAL104533          0
IS-V24-INTERFACE                         FAL104532          1
ISDN-TERMINAL-INTERFACE                  FAL104453          0
LINE-INTERFACE-MODULE                    FAL1040049         4
MOBILE-EXTENSION                         FAL1040525        50
OM-ETH-INTERFACE                         FAL104540          2
OM-V24-INTERFACE                         FAL104539          5
OPERATOR-EXTENSION                       FAL104456          4
PAGING-LOOP                              FAL104518          0
PAGING-PARALLEL                          FAL104519          0
PAGING-SERIAL                            FAL104517          0
PERSONAL-NUMBER-USER                     FAL104472      65535
RADIO-EXTENSION                          FAL1040285         0
REPEAT-IND-DIV-USER                      FAL104471      65535
RVA-EXTERNAL                             FAL104487          0
RVA-INTERNAL                             FAL104486          0
SMDR-ETH-INTERFACE                       FAL104489          0
SMDR-V24-INTERFACE                       FAL104488          1
VCU-FAX-III-PORT                         FAL104512          0
VM-ETH-INTERFACE                         FAL104535          0
VM-V24-INTERFACE                         FAL104534          1
VOICE-MAILBOX                            FAL104470          0
VOICE-PORT                               FAL104547          0
VOICE-SYSTEM                             FAL104546          0
VOIP-ETH-INTERFACE                       FAL104707          1
                                                             
SYSTEM LICENCES                                              
                                                             
LICENCE TAG                              FAL          ALLOWED
A-NUMBER-DISPLAY-ATS                     FAL1041997        NO
ANCD-FEATURE                             FAL104545         NO
DISA-NUMBER                              FAL104484         NO
DUPLICATED-GS                            FAL104524         NO
HOSPITALITY-APPLICATION                  FAL104709         NO
NET-SERVICES                             FAL104506        YES
ORIGINAL-A-NUMBER                        FAL1040278        NO
QSIG-CALL-OFFER                          FAL1041985        NO
TRAFFIC-MEASUREMENT                      FAL104485        YES

[red] LONDON [/red]

<syidp;PRIVATE NETWORK EXCHANGE IDENTITY IS                             
71100                                                       END                                                         <roddp:DEST=71200;EXTERNAL DESTINATION ROUTE DATA                       
DEST  DRN ROU CHO CUST ADC                        TRC SRT NUMACK PRE    
71200     60           0626100000000050006000000  5   6   0      71200  
END                                                         
<rondp:rou=60;ROUTE NUMBER DATA                                         
ROU   PRE   ROUDIR   EXNOPU     EXNOPR     TERAC                        
60                              6-71100                                 
                                                            END

[red] ROTTERDAM [/red]

<syidp;                                                                   
PRIVATE NETWORK EXCHANGE IDENTITY IS                                      
71200                                                                     
END                                                                       
<roddp:dest=71100;                                                        
EXTERNAL DESTINATION ROUTE DATA                                           
DEST  DRN ROU CHO CUST ADC                        TRC SRT NUMACK PRE      
71100     60           0626100000000050006000000  5   6   0      71100    
              
END                                                         <rondp:rou=60;
ROUTE NUMBER DATA                                                         
ROU   PRE   ROUDIR   EXNOPU     EXNOPR     TERAC                          
60                              6-71200

[bold]
So any ideas on what i have missed?
[/bold]




[red]Striker : My orders came through. My squadron ships out tomorrow, we're bombing the storage depots at Daiquiri at 18:00 hours. We're coming in from the North, below their radar.[/red]
[blue]Elaine : When will you be back?[/blue]
[red]Striker : I can't tell you that? It's classified.[/red]

 

[whosrdaddy]

alchohaz,

give full info plz :

RODAP:ROU=X;
ROCAP:ROU=X;
RINIP:LIM=1;
RIANP:GRP=X;


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

 

[mundus]

Hi' maybe this could be a solution, use nutri;
NUTRI:ENTRY= ,CNVTYP=1,NUMTYP=11,TARDST=71100,PRE= ;
where ENTRY is the exchange extension number series and the PRE is what you want to pre the extension A number with, don't forget to set the RODDI ADC d24=1 where this NUTRI shall be executed.

 

[whosrdaddy]

mundus,

cnvtyp 1 wont work for transit calls...

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

 

[Isinor]

Hi, have you tested whosrdaddy's settings? Because you TRC=5 which removes 71200, then you PRE 71200 to put it back again… strange... then you SRT on 6 which does not send 71200 to the network... even more strange, but it should work...

What is in the display on a digital phone in Rotterdam ?

I know this works on QSIG (TLU-76) routes, but have never tested it on an IP route…

London...
roddi:dest=71200,rou=60,adc=0606100000000050006000000;
rondi:rou=60,exnopr=6-71200;

Rotterdam...
nansi:numtyp=en,numse=71200;

And the equivalent for the return trip. No TRC no PRE no SRT they are not needed.

RODAP:ROU=X;
ROCAP:ROU=X;
Route categories might have settings that are the problem...

Regards
Isinor