Appreciate any inputs on my query?

Just realized that I didn't give the version details. Environment is Avaya IC 7.3.5

Can someone please guide me how to update the datbase server details?

Here is the situation I am facing in one of my project -

Client wants to move from SQL 2008 to 2016. In line with this, IC server should be pointed to the new 2016 server. I made the changes in the corresponding ADL files via Database Designer and restarted Directory services/Data services (from IC Manager) refresh is success. However, I am seeing the changes are not effected i.e. still the IC is pointing to the old database server (checked via Dataserver --> advanced --> server status --> Pool1.

Appreciate your help and Thanks in advance!

Ok Wilson!

Thanks for your answers

Thanks Wilson!

monitoring the GC and class instances are to fine tune the heap size -- that is the next step. First step is to what value should we set during the initial installation /commissioning of websphere server.
Please advice.
current IVR application takes about 50k calls per day with a max concurrent calls of 500 during peak hours

Thanks,
Srini

At the client place, we are upgrading the IVR application to OD7.1 (from DD5.1) and moving to Websphere from Apache Tomcat.
As part of the sizing, how do we arrive at the heap size range (max and initial). Also, any configuration tuning needs to be done at Websphere end so that we take the full advantage of the available heap size.

IVR application takes about 50k calls per day and the max number of concurrent calls is about 500 (during peak hours)

Please advice.

Regards,
Srini

Thanks Wilson!

Yes Wilson - you already mentioned this.

what I was trying to ask in my previous question is (I should have mentioned explicitly though) - is this not possible using DD/OD's bridge transfer node and why?

Thanks,
Srini

Thanks Wilson!

We understood that the 3rd party application doesn't support UUI. Can we pass the digits as DTMF while using bridged transfer control using DD 5.1? please advice

1) Caller calls IVR1 and enter account number
2) IVR1 application uses bridge transfer and dials out the external 1-800 NUMBER to reach another IVR application
3) As soon as the call gets connected, IVR1 pass the caller entered digits as DTMF (no attach data) to the destination IVR and then complete the transfer.

Data that we mention in the AAI field is not received at the destination IVR side. Any specific encoding format to be followed as the data has to traverse via external network.

Please advice.

Thanks,
Srini

So, in your opinion, can't we accomplish this task via OD/DD?

I would like to explain the steps again for your reference
I have two IVRs (say IVR1 and IVR2) that are connected via external carrier network.
Step 1 --> IVR1 answer the customer call, receives the input and dials out external number to reach IVR2 (caller is on hold)
Step 2 --> IVR1 sends the collected input as DTMF digits to IVR2 after few seconds of delay after step1 (customer is on hold)
Step 3 --> IVR1 completes the transfer so that caller is connected to IVR2 (now IVR1 is disconnected from the picture)

If I complete step3 before step2, this means that IVR1, IVR2 and caller will be in conference (3 party conference) and then IVR1 has to disconnect. I am ok with this approach as long as we can send the data as DTMF digits. Is that possible using OD / DD?

Thanks,
Srini

Thanks Wilson!

Instead of listening to the BEEP tone, is there a way of sending DTMF digits with a delay of 2 seconds?

can we make the bridge transfer scenario to work on the following mode?
1) IVR dials out the external 1-800 number
2) IVR waits for 2 seconds and then sends the digits
3) connect the caller with the called party

Please advice

Regards,
Srini

Hi All,

From Orchestration Designer, call has to be transferred to an external IVR application over the network. Using the bridge transfer node, we dial the external 1-800 number. Once the external IVR answers the call, it sends a BEEP tone. From OD, how to recognize the BEEP tone at far end (destination IVR) and send the digits as DTMF tones before connecting the call. Can you please help?

Please note that the destination IVR doesn't support UUI.

Thanks,
Srini

I am also facing similar kind of issue while trying to transfer the call *<FAC>#<VDN>#<Collected digits>.

Anything to be configured at the switch side explicitly? Do you have any pointers on how to collect the digits at the PBX/Switch level? Any help is appreciated.

Thanks,
Srini

Hope you are feeling better now. Please keep me posted once you get some response on this.

Also, can you please share any useful pointers (docs, links) on the advance segmentation sever? can that be hosted in VMWare (this is for development environment)?

Regards,
Srinivasan

Thanks for the explanation!

When Avaya mention 7.2 has reached End of life, I assumed that is applicable to all the sub-releases within 7.2 i.e. 7.2.1 through 7.2.6 Please correct me if I am wrong

If I look into the document you have shared, it was mentioned under the section "Migration Strategy" that customer has to upgrade to 7.2.6 i.e. Avaya recommends that all Avaya Interaction Center/Operational Analyst 7.2 customers upgrade to the latest Service Pack 7.2.6 or R7.2.7 (when available) or AIC R7.3.x

So, does this mean that, 7.2.6 is still supported?

Regards,
Srinivasan