E1 Logical clubbing in PRI

surya · Post by **surya** » 01 May 2015 01:26

We have a problem in our OXE. we have taken licence to integrate Our OXE extentions with our cellular network operator (Our employees use same network , company provided SIM). We have our numbering plan like this. 72xxx - 75xxx (Total of 4000 extentions and 5 digit number plan). we have taken licence for 4 PRI or 4 E1 (120 voice channels) with the same levels (the number plan of network operator is 2xxxxx). So they created 4 DID levels
=>272xxx = PRI1
273xxx = PRI2
274xxx = PRI3
275xxx = PRI4.

Note: digit "2" is added before our OXE extention number to make it compatible with no. plan of other PBX
In india the mobile no. is of 10 digits and including country code (91) it is 12 digits. My area STD code is 06542. So 916542-27xxxx, will make the numbering plans equal. when we dial from OXE extension, we simply dial "0" (trunk access code) and the mobile number. when we are dialing from
mobile, we dial 06542-27xxxx. The problem now is when we dial a extention number from lets say 272xxx and if that access the PRI1 voice channels
then CLID is fine other wise if it accesses the PRI2,3,4 voice channels then it is showing the pilot number like 06542-272000 or 06542- 273000 as CLID. How can i configure my OXE so that it shows the actual CLID, irrespective of which PRI (1 or 2 or 3 or 4) it accesses not the pilot number. i am a novice, if i couldnt use any specific technical terms in describing my problem excuse me.

Konstantinos.E · Post by **Konstantinos.E** » 01 May 2015 03:52

what about transcoding in your trunk groups or entity ? discriminator rules ? show us your config ..

Sent from my iPhone using Tapatalk

tgn · Post by **tgn** » 01 May 2015 06:20

build different trunk groups (one for each access) and configure ars feature.

regards...

Post by **tot3nkopf** » 01 May 2015 09:01

Or request your provider to configure all numbering ranges in all trunks --> helpful also for redundancy.
In this way you can use the same trunk group.

Konstantinos.E · Post by **Konstantinos.E** » 01 May 2015 12:29

I thought for incoming ... you can use also entities ..installation number and supplement number ..

Sent from my iPhone using Tapatalk

surya · Post by **surya** » 02 May 2015 00:12

Can we create a COS where a particular series extension number will access the specified trunk only. Lets say any number in Level 272xxx will access only PRI1 channels or level 273xxx will access PRI2 channels and so on..like this.

surya · Post by **surya** » 02 May 2015 00:14

Thansk for the replies. @tot3nkopf: we had that discussion with the service provider, as thats a government run entity here in India, they are very adamant and they are saying they not club the PRIs and they will only give 1000 extensions in a single levels. So we are thinking of doing any configaration changes in our side.

tgn · Post by **tgn** » 02 May 2015 08:16

surya wrote:Can we create a COS where a particular series extension number will access the specified trunk only. Lets say any number in Level 272xxx will access only PRI1 channels or level 273xxx will access PRI2 channels and so on..like this.

A COS will not help. declare an entity for each (272xxx and 273xxx). in the entity you have an option trunk group, which can be used as route source in the ars route. for more information consult the docs.

regards...

surya · Post by **surya** » 04 May 2015 00:09

@tgn: Thanks for the reply. I think it might help me. let me do this and i will get update you again.

Alcatel Unleashed