Big problem with no solution??

[aprasha]

Well...Suppose that I have 2 MDs in different countries (RUSSIA and EEUU, for example), connected by a Tie-Line.
Of course, I use that Tie-Line for calling from EEUU to a Russian's number to save money, but that makes me have a "little" identification problem.

Of course, the number sent to PSTN is a Russian number (the principal ISDN number of my PSTN Russian Trunk).

Here's the problem: I want this number to be another of my Russian ISDN numbers, not the principal one (I don't know the name for this number in English, but I hope you understand what I mean).

First solution:
Using ROUDIR.
Problem: The INTERNAL callings between both MDs are also modified, and I want to keep this feature.

Second solution:
Using NUTRI: CNVTYP=0, NUMTYP=6
Problem: I can get the callings from the other MDs through the PSTN route, but with NUTRI you only can modify B-number, and I need to change the A-number.

Third solution:
Using Cust for incoming Route.
Problem: There's no command for assign a Customer Number to an Incoming Route.

Fourth solution???????

Thx for help! but this time I think it has no solution
The calling identifies with the principal number of the PSTN that corresponds to

 

[aprasha]

P.D.

Forget the las phrase ("The calling indentifies....to&quot. It's a mistake. I haven't have lunch yet

 

[SYAR2003]

Is this a real problem (implemention planned) or is it a
thought experiment .

Note! Only local a-numbers will be allowed
by the public as you say .
So use the NUTRI in combination with ROU to control
the a-number prefixing from the EEUU side.

syar

 

[aprasha]

It's a real problem, but the countries are ficticious. I'm having this situation but between two islands.

I'm trying to understand your explanation, but I can't. Maybe my previous explanation was not good:
When i said "Of course, I use that Tie-Line for calling from EEUU to a Russian's number to save money", I'm talking about an EEUU MD making a call to a Russian number, BUT NON OF Russian MD (an external Russian number). For example, Boris Yeltsin's home
I do this easily, but the number that Boris see on his phone is the "principal number" of my russian PSTN trunk.
That number is the same when a non-integrated extension of my Russian MD calls Boris Yeltsin. And this is the problem. My boss wants that EEUU pay their Russian public calls and Russia pay their own Russian public calls (including non-integrated extensions calls), but no using CIL but watching the Telephonic Public Account that comes every month from the Public Enterprise that manage the PSTN trunk.
Sorry about my englis, but I hope you understand now.

If you did it before, please, explain again your answer cause I couldn't understand it.

Thx a lot!!

 

[SYAR2003]

If your tie line supports transfer of a-number
the md in russia's NUTRI:entry= ,rou=tie,cnvtyp=2,trc= , pre=new-a-number;

Taking the a-number from EEUU tie-line truncate all digits
and forming a new one with pre parameter .

That's a way to do it.

syar

 

[aprasha]

Yep, but in BC10, you only can use up to 5 digits in PRE, but I need at least 6 . In BC11 it's up to 20 !!
I think we are going to update to BC12, but I really want to know if this will fix the problem.
Here's an example:
EEUU extensions: 1xxxx
Rusia extensions: 2yyyy and 3zzzz
Russia public number: 34567yyyy and 34589zzzz

I want that EEUU extensions calling public Russian numbers will indetificate with the number 345679999

RONDP of public route (ROU=1)in Russia side:
ROU PRE ROUDIR EXNOPU EXNOPR TERAC
1 0-345

NUTRP in Russia side (for outgoing numbers to public PSTN):
ENTRY CNVTYP NUMTYP ROU PRE TRC
2 1 10 67 1
3 1 10 89 1

The solution would be??:
ENTRY CNVTYP NUMTYP ROU PRE TRC
1 1 10 679999 5

Is that true? Will it works? (I need to be sure, cause if I upgrade and then it doesn't work....well...you can imagine).

Thx!!!

 

[mdman]

In transit calls you can also add prefixes with the command ROAPI. You set this on the incoming route and the prefix will only be added if the call goes transit, if the call terminates in the Md110 this prefix will not be added.

 

[SYAR2003]

I know it will work , because i've done the same
setup for a MD30 in transit to a MD110(BC11) and calling out on the MD110 to pstn with correct a-numbers (though in same country)
It may of course possibly be some tuning involved ,
setting the right data here and there .

You tie the NUTRI's to the outgoing route on the "russian" end with the ROU parameter (programmed in the "russian" MD)

syar

 

[aprasha]

For mdman: Thx, but there was another problem....In "Russia", I have 3 MDs!! (and when EEUU calls the second or third MD, the extension number (A-number) is modified, and I don't want that...

I'm tired of thinking with all the posibilities (RONDI, NUTRI, ROAPI, RODDI...) and I think, the best way to resolve this is waiting for BC12 and do the NUTRI with the desired PRE.

Thx all indeed!!