MrAnMo wrote:do some modification when the incoming trunk is a private call
Whould you share how you do it?
A4400 was not a transit pbx, it were some project to include SS7 or use ATM (search for pra7 cards in around R3 or search ATM155 cards up to 5Ux) but it was a quick 'phase out', still having in menu, and sometimes need to explain to end-customers: no-way. It's only empty caption in a menu, it does not work.
As for transit, try this: call goes in, you put it to a number like 2200, 2 it's an Abbreviated Number to dial DISA, in DISA you use automatic substitution (if you got CLI), and 200 is Abbreviated Number to dial out somewhere else.
Also see this: if you have PBX"a"->A4400->PBX"telco" connected by DSS1 you can't pass a CLI with CLIR flag on, to say this: PBX "a" sets CLI to "12 000 000" but it puts the CLIR flag on, what does A4400 on this picture ? it removes CLI from DSS1 (acts as end-user pabx, not the transit one) so PBX "telco" sees empty CLI plus a CLIR flag. So PBX "telco" must put any CLI on that call to pass it through a national carrier network (even when it's CLIR).
It's a not a request that ALU will agree to do it, if you want this, ask for products for TELCO / carrier grade. You will have full range from S12 or E10 to small (
~200 x E1) compact switches from Lucent. Also ALU's BP for OXE/OXO don't have channel to buy such a transit pbx, you must search for carrier-level partner of Alcatel-Lucent.
Anyway: i try to convince everyone who tries to use a4400 as transit pbx not to do so, it's a great corporate or CCD pbx with IPT capabilities, but does not fit the 'carrier-level'.
Please note that at no time I will provide you with OXE/4400 nor AOS releases.
Note that it's our private time, that we spent to help you, so please don't expect complete solution for your problem.
You will need to do homework by your self.