Avaya Support Forums  

Go Back   Avaya Support Forums > IP Office Contact Center

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 04-07-2016, 05:36 AM
singh414 singh414 is offline
Member
 
Join Date: May 2014
Posts: 9
singh414 has 10 reputation points
Default Caller Number for call Back request to be displayed on Agent screen

Hello All,

We are using a simple call back option for giving a caller to leave a call back option.

Once the next agent is available the call back is made and it is working fine but the number which gets displayed on the Agent screen is the topic number on which he has left a call back request.

Is there a way that instead of displaying the topic number details on Agent screen the actual called number can be displayed. Any suggestion to achieve this would be of great help.

Thanks & Regards,
Singh414
Reply With Quote
  #2  
Old 04-07-2016, 11:19 AM
kruegerb kruegerb is offline
Genius
.
 
Join Date: Oct 2013
Location: Stuttgart-Germany
Posts: 276
kruegerb has 12 reputation points
Default

How is the call back configured ?as dialer call job?
.
Reply With Quote
  #3  
Old 04-15-2016, 12:03 AM
singh414 singh414 is offline
Member
 
Join Date: May 2014
Posts: 9
singh414 has 10 reputation points
Default

Hello Kruegerb,

We are using a simple call back IVR call flow present in the IPOCC installation folder in which caller leaves a call back request during out of office hours with topic ID, CLI, and call job details getting inserted in the database. During the next available agent time a call back is made by the dialer using a topic ID on which call back has been left.

Thanks & Regards,
Singh
Reply With Quote
  #4  
Old 04-22-2016, 08:03 AM
kruegerb kruegerb is offline
Genius
.
 
Join Date: Oct 2013
Location: Stuttgart-Germany
Posts: 276
kruegerb has 12 reputation points
Default

That is not normal behaviour . Normally the destination number is shown.
Some things special? Trunk type? Phone Typ? Which version ,especially Ipotaskserver?
Reply With Quote
  #5  
Old 04-24-2016, 10:43 PM
singh414 singh414 is offline
Member
 
Join Date: May 2014
Posts: 9
singh414 has 10 reputation points
Default

We are using 9.1.6 and this is being faced on Avaya console which is integrated on Salesforce portal.

It is normal E1 trunk with IP phones
Reply With Quote
  #6  
Old 05-02-2016, 02:13 AM
kruegerb kruegerb is offline
Genius
.
 
Join Date: Oct 2013
Location: Stuttgart-Germany
Posts: 276
kruegerb has 12 reputation points
Default

I see. that's an issue of the sales force client, during preview time only the topic name is displayed, in the moment the call to destination is started (ringing at destination) and during conversation the destination number and in case of known customer the Name from Salesforce is displayed.
In case of using IPOCC UI or WebUI also during preview time the number is displayed
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 08:48 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.