Hello,
We are in the process of vetting the soft phone portion of this application before moving forward and having some issues. We are on release 7.1 for CM, System and Session. We copied our current 46xxsettings file and renamed it so this application only pulls info from the test txt file. Had our DNS group build the PRT, SRV and TXT records for it to query. From what I was reading in the very vague documentation nothing really to change in the settings file. When opening the client (Windows) enter the email address and it logs in, but then we have to log out to configure the phone and calendar piece. Once we do that we can make outbound calls but the inbound do not work. We get a message when you click on the people icon on the top left to sign out of "No incoming call features available". We set this up as TCP so we wouldn't have to add the certs and the station is built as dual registration. If anyone has any ideas on how to get this message error resolved so we can receive calls I would appreciate it. If the testing proves successful for the client then we would be looking to do an Avaya Device Services deployment.
Thank you,
We are in the process of vetting the soft phone portion of this application before moving forward and having some issues. We are on release 7.1 for CM, System and Session. We copied our current 46xxsettings file and renamed it so this application only pulls info from the test txt file. Had our DNS group build the PRT, SRV and TXT records for it to query. From what I was reading in the very vague documentation nothing really to change in the settings file. When opening the client (Windows) enter the email address and it logs in, but then we have to log out to configure the phone and calendar piece. Once we do that we can make outbound calls but the inbound do not work. We get a message when you click on the people icon on the top left to sign out of "No incoming call features available". We set this up as TCP so we wouldn't have to add the certs and the station is built as dual registration. If anyone has any ideas on how to get this message error resolved so we can receive calls I would appreciate it. If the testing proves successful for the client then we would be looking to do an Avaya Device Services deployment.
Thank you,