Customer environment:
Avaya Communicator CP 2.0.3.70
IP Office Server Edition 9.1.9
With One-x Portal currently running on Diagnostic patch oneXportal-9.1.902-10.rpm which was provided in IPOFFICE-118432.
BBE lab environment:
Avaya Communicator 2.0.3.70, 2.0.3.30, 2.0.3.33, 2.0.3.55 and 2.1.3.0 IPO Server Edition 9.1.6, 9.1.8 and 10.0.0.3
Details:
In One-x Portal Client, add a personal contact with Work Phone, Mobile Phone and Other Phone. Set Primary Phone accordingly.
Example:
I logged-on as Agentt1, then I added personal contact for internal user Ruel2. I added Work Phone as 3004, Mobile Phone as 02041217777 and Other Phone as 094765555. Then I set the Primary Phone as Work Phone.
Agentt1 is currently logged-on on Avaya Communicator.
Now, I made a call from extension user Ruel2 extension 3004 to Agentt1. It doesn't matter whether Agentt1 answered the call or not. Then after the call, check the Call History. The phone number will show is not Work Phone but rather Other Phone. Because of this, when Agentt1 decided to call back 3004 from call history, it would then dial the Other phone instead of Work Phone.
I've tested with multiple Avaya Communicator versions as well as IP Office Server Edition versions. It appears that this issue is present in release 9.1 and 10.0.x.
Additional info:
If in One-x Portal client under Contact, Primary Phone is set to Work Phone, Avaya Communicator Call history shows the number as the “Other Phone” number.
If in One-x Portal client under Contact, Primary Phone is set to Mobile Phone, Avaya Communicator Call history shows the number as the “Other Phone” number.
If in One-x Portal client under Contact, Primary Phone is set to Other Phone, Avaya Communicator Call history shows the number as the “Mobile Phone” number.
