Need to manage two ANI number on outband calls

[aflores]

Hello all, Hope everybody is fine.

I got a situation on a system A4400 (R3.1) and two different Operators,

Both operator (carriers) are conecte to the 4400 through an E1 MFC-R2 link independent of each other.

Need that, when a user make an outgoing call through Carrier_1, the identification numbre must be acording the Carrier_1 numebering plan and, if the same user make a an outgoing call through Carrier_2, the identification numbre must be acording the Carrier_2.

Carrier_1 numbering plan start with 212 308 1xxxx
Carrier_2 numbering plan start with 212 208 1xxxx

In both cases, the 1xxx are de 4 digits extesntion´s numbers user.

Both Carriers needs to receive the complete numbering to allow the outgoing calls.

I have manage the NPD Selector and also (just to test) the Installation N° (ISDN) parameters with no result.

By the way, the incomming calls with the two carriers is working fine.


Any hint will be apreciated.

Regards.

AFlores

(PD: And yes, there are still some dinosaurs in the Alcatel 4400 / Enterprise world.)

[vad]

"I have manage the NPD Selector and also (just to test) the Installation N° (ISDN) parameters with no result." - what do you mean?

If you manage for NPD - Calling|connected DID with rules - 2123081xxx - 1xxx - what PBX send like ANI?

[oldboy]

So i guess a question how are you seizing the Trunk to make an outgoing call??

If ARS simply the NPD and DID as Vad mentioned above will do all the work for you, but i guess you will need 2 ARS seizure prefixes

[oldboy]

So i guess a question how are you seizing the Trunk to make an outgoing call??

If ARS simply the NPD and DID as Vad mentioned above will do all the work for you, but i guess you will need 2 ARS seizure prefixes

[aflores]

Hello everyone, thanks for your responses:

Before writing the post, we had already discussed the configuration you suggested.

I don't think I explained myself well:

There is only one prefix for making outgoing calls. The first option is the Carrier_1 trunk group, and if it is busy, it overflows to Carrier_2.
So, when calls are sent through C1, they flow without problems, but when calls are sent through C2, the calls are rejected because the C1 ID is being sent to C2, and C2 obviously doesn't authorize or recognize it.

Exactly as detailed, the solution would be two different prefix numbers for each carrier, but the client doesn't want it that way. The call should be transparent for the caller, meaning they don't have to dial different prefixes.

Having to dial two prefixes, depending on whether the outgoing groups are busy, is annoying.

They do not accept two ARS prefixes.

Thanks for yous replies.

AFLORES

[aflores]

Hello again.

Finally we got a soluction.

We manage two different NPD Selector, one for each trunk group (originally we were using the same NPD Selector for the two tg and the default NPD)

We cretae two NPD 34 and 35 and on the parameter: example of one of them:

Consult/Modify: Numbering Plan Description

Node Number (reserved) : 1
Instance (reserved) : 1
Instance (reserved) : 1
Description identifier : 34

Name : (Carrier_1 or 2 )
Calling Numbering plan ident. + Unknown
Called numbering plan ident. + Unknown
Authorize personal calling num use + False
Install. number source + NPD source
Default number source + NPD source
Called DID identifier : -1
Calling/Connected DID identifier : -1
Installation number : 2123081
Default number( num. inst. sup.) : ------------------------------



wen we configured the "Install. number source" parameter as: "NPD source" automaticaly apears the paramater: Installation number: and put the identification number of the carrier so, now, each outgoin call sent the corresponding information.


Regards

AFLORES