" /> Having two OCS servers in a single Tenant - Genesys CTI User Forum

Author Topic: Having two OCS servers in a single Tenant  (Read 4613 times)

Offline fjveca

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
Having two OCS servers in a single Tenant
« on: June 20, 2012, 07:46:20 PM »
Advertisement
Hello, I'm really new at handling the Genesys Platform and I have a very simple question to ask

I've been in the need to have more than one outbound code in the OCS server but I haven't seen a way to do this which lead me to my first question.

can I have 2 OCS servers in the same Tenant each one with a different outbound code, or do I need a multi-tenant enviroment to have 2 OCS servers?

thanks beforehand if anyone has the answer for this I would be very grateful

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Having two OCS servers in a single Tenant
« Reply #1 on: June 21, 2012, 03:53:45 PM »
why not? Each OCS can have its own TServer or even a single one but handle different campaigns...but...why???

Offline fjveca

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
Re: Having two OCS servers in a single Tenant
« Reply #2 on: June 22, 2012, 06:35:32 PM »
Thanks for the reply, I finally found a simple solution for the problem I had, you can actually set a Public_Network_Access_Code in the Annex of the Campaign list and have the PBX handle which trunk are you going to use instead of having 2 OCS each one with a different PNAC.

BTW we are using a 7.2 version of the OCS and this is just my second week handling the platform so excuse me for not knowing this kind of details, so that part is working fine but I'm having trouble to set the ANI, I've modified the CPD server's Calling_Party_Number to a number I'm interested to be displayed on the destination phone but all I keep getting is the main number of our ISDN E1 instead of the number of that E1 that would have to be shown, I've talked with my telephony providers and they say that they aren't restricting the ANI selection as long as we are in the ISDN E1 range number assigned to us.

so the question would be: is there any parameter left where I should put the ANI I want to show?

as of now the Outbound is connected to a PBX Alcatel 4400 at least that's what I've been told.

again thanks for answering my previous question.

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Having two OCS servers in a single Tenant
« Reply #3 on: June 22, 2012, 07:38:20 PM »
Another option is to put the dial prefix into the customer_phone for each record on the calling list.
ANI? You mean the customer identification number? But in outbound there no such...what exactly do you want to show?
On OXE you can do many things but first would like to understand fully what is your goal.

Offline fjveca

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
Re: Having two OCS servers in a single Tenant
« Reply #4 on: June 22, 2012, 08:13:09 PM »
Well the goal is very straight forward, as of now there is an inbound contact center that handles calls from the customers which can't accept or simply missed the call of the outbound campaign, that Contact center is reached by one specific numer when you dial from the street lets set an example number (212-555-7778), if you dial that number here you will get to a queue with agents that will process the call.

I need that the outbound call identifies itself with that number exactly for two reasons, up until now the outbound calls were handled in a way where the number displayed in the contacted client phone was set to "unknown" so they didn't know who was calling them, but now they need a certain number of campaigns to show the number so the customer can call back if they can't take that call in any of the N number of attempts the outbound campaign makes.

in principle the first problem was solved since I can configure the calls to go out in a different Trunk by giving a different Public_Network_Access_Code to the campaign that needs to display the ANI in the outbound call that sends each call for a trunk that Hides or doesn't hide the Calling Party Number/ANI/CallerID according to our needs.

and here is where I'm actually stuck now, when the outbound call reaches it's destination the ANI I see is the main number of the E1 trunk let's say it is (212-555-7700) instead of my desired ANI (212-555-7778).

as I said previously in the CPD I set the Calling Party Number for 212-555-7778, as far as I know that's the ANI that should be displayed on the phone who is getting the call but for some reason I get the main number of the E1 trunk instead.

I hope I didn't make the scenario too confusing.

again thanks beforehand for the any information that could help

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Having two OCS servers in a single Tenant
« Reply #5 on: June 23, 2012, 04:20:53 PM »
Well not confusing but just wanna be sure:
Trunk Group A used for Inbound calls is exactly the same as the one used for Outbound calls.
If yes we are ok
So you can't manage that on CPD only...you have to manage the NPD tables on OXE and then configure the dialers (VirtualZ extensions)...ask them to take a t3 trace and see what is going on

Offline fjveca

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
Re: Having two OCS servers in a single Tenant
« Reply #6 on: June 25, 2012, 03:45:56 PM »
thanks and yes the same trunk will be used in this case for Outbound and Inbound.

OK a coworker found what was going on, it seems that the PBX is only accepting ANI numbers of 4 digits long, and then it adds the preceding digits, at least that's what they told us, so when we set the CPD to send the last four it worked just fine, because when more than 4 digits was delivered it used the default number for the E1 trunk.

so now that part is more or less solved, but now the higher ups are asking me if it is possible to set specific ANI per outbound campaign, so far the only way I've managed to see that is having multiple CPD where you can actually set the Calling_Party_Number for each CPD and assign the corresponding CPD server to the Campaign, but that would mean having one CPD for each ANI that needs to be displayed, which seems like a lot of licences and servers if you want for example to set 4 campaigns each one with a different ANI showed in the destination number.

Is there any other way that I've been missing out, can I configure this by campaign basis as the Public_Network_Access_Code? or did I just hit the limits of what this instalation can do?

Thanks beforehand

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Having two OCS servers in a single Tenant
« Reply #7 on: June 25, 2012, 07:24:08 PM »
Ask you OXE guys, maybe with different prefixes and different NPD for them so you have each campaign with its own prefix and translation table