Page 1 of 1

Call transit to two different operators

Posted: 16 Jan 2013 08:28
by slabr
Hi all.

I've got such a config: CUCM8.6<=T2-QSIG_ABC_F=>OXEr9.1<==>T2_ISDN_Operator1
\<==>T2_ISDN_Operator2
Can it be possible to transit calls from CUCM to both operators with different pool numbers? Unfortunatelly, Operator1 has one pool of DDIs and can show in setup only this pool and Operator2 has another pool od DDIs and can setup only his pool. As I know, during transit call it is based on Entity number of Trunk group (in my config beetwen CUCM and OXE) and proper discriminator numerd assigned to Entity. So should I have two different T2 trunks beetwen CUCM and OXE assigned to two different Entities to be possible proper transit calls to both operators or maybe there is a possibility to do it on one T2 trunk?

Regards
Slawek

Re: Call transit to two different operators

Posted: 16 Jan 2013 18:18
by tot3nkopf
You can do it as for usual users belonging to one entity (in your case the one of the transit trunk group).
- you send ARS seizure in front of the external number from Cisco
- you need 2 NPD's for external trunk groups, one using for instance DDI translation table 1 and the other one to DDI translation 2

(of course other configs like: discriminator, relation between logical discriminator and actual discriminator in entity, ars routes, ars prefix must be configured)

Re: Call transit to two different operators

Posted: 17 Jan 2013 14:04
by slabr
I've got everything configured for two operators (NPD, discriminators, etc.) and all is working correctly in both directions in OXE. But incoming number from CUCM will also be processed as from OXE? I mean, if I'd like to make outside call from CUCM through OXE, the outgoing number will be processed by ARS rules as OXE outgoing calls?

Re: Call transit to two different operators

Posted: 18 Jan 2013 05:15
by tot3nkopf
As I remember yes. I think trunk group should be private and network mode enabled.
You should test this.