Calling number modification?!

[Billy]

Hi there. OXE R9.1.

Historically my OXE was connected to PSTN with only one TDM trunk, a regular PRI. Behind the PBX are two clients connected to it with PRI also. I had three trunk groups.
TG1 -> PRI -> Telecom1 -> PSTN;
TG100 -> PRI -> client 1;
TG101 -> PRI -> client 2.
The numbering plan is quite simple: 0 = Professional TG with overlapping - any dialout goes to TG1. Calling numbers are generated by clients' PBX and were 7 digits long (local open numbering).
Now I've subscribed to another operator (Telecom2) and have a SIP trunk to it (say TG2). The new operator requires Calling numbers to be 11-digit (full international) but I'm bound to two things: a thousand of subscribers in client1 and client2 companies, and Telecom1 which is still satisfied with 'local' numbers. Can't change ALL this in a moment!

The question is: How can I add those country and area codes to a call going from TG100 to TG2 but not to TG1? I've tried DID translator in NPD's assigned to both trunk groups, but it works only for 1 number, whilst both clients have 10+ non-contiguous PSTN numbers each.

Thanks!!!

[dryhouse]

you can do it using ARS option "digits to add" on ARS table of TG2...

Regards..

[Konstantinos.E]

Hi

play with Entities and instalation number and assign the trunk group to the entity that you want.

[Billy]

dryhouse, calling number, not called.
Konstantinos.E, please explain. Even if I'm able to prefix a calling number with entity installation number, HOW do I assign different entities to one trunk?? I need to send 7 digits to one Telecom, and 11 to another.

[dryhouse]

Sorry,... do you try changing NPD in ARS table?

[Konstantinos.E]

a ok..now i understad what you want to do....

just a thougt..

in discriminator rules how many digits do you assign? 7? do it 255

[vad]

For transit calls from ISDN:
OXE will do something with calling number only - if incoming TG - private=yes and network mode=yes.

F.e. for outgoing TG (or ARS route) manage NPD with installation number and DID=-1 - For transit calls will be added installation number to recieved Calling number.
But will some problem with accounting (absent tickets to private TG direction) and calls to private TG (f.e. when OXE user calls to private TG - installation (or suppl. inst. number) from user Entity will be added to CALLED number - use NPD source instead of Entity source.

[Billy]

You may laugh but I'm sitting now a whole day long trying to manage an ARS callout even with no A-number mangling!!! If an user on that TG dials 0 (Professional TG with ovl that goes directly to PSTN) it does connect, but if he dials 9 (the ARS prefix) - it gives some second of silence and then drops the call...

[vad]

not uderstand - 0+number and 9+number - problem with transit calls? If yes usually can be some problems:
- DID translator for incoming TG (if used);
- For ARS prefix (if used discriminator different from 0 and 1) - you need to check Entity/ discr. selector from incoming TG entity (default 0);
- block mode dialing (f.e. 0+number recieved in block, 9+number - no) - easy to check with t3 trace;
- if incoming TG - private with barring in local parameters - used public network COS from incoming TG.

[Billy]

vad,
0+number = ok either if called from client's TG or from an UA/Z extension;
9+number = ok from UA/Z but not from TG: some seconds of silence and then disconnect.

Client's TG parameters: no DID, Entity = 10 (is it ok?), discriminator selector is logical disc 3 -> physical disc 3;
ARS prefix = 9 with disc 3;
Overlapped dialing = YES, t3 shows Normal Call Clearing - traced shows nothing !!!
No barring/PIN, tried both public and private, same eggs... (grin)

Most likely there's something in the cos hash, i'm not familiar with it - but there's no much restrictions anywhere.