We are having a similar problem using RTD through a firewall. Can it in fact be done? Using a sniffer to look at port usage, we see connections on a number of static ports, but one connection where a random port number chosen by the RTD client is sent to the CCM. CCM then turns around and connects on that random port. A firewall killer, for sure.

Can anyone provide an guidance on whether and how to connect RTD through a firewall?

Audrey -

Can you confirm a few things we are seeing with Avaya's SFDC plug-in?

The customer must be using Enterprise Edition or better - the plug-in can't be loaded if using Professional Edition.

For a pop on phone number to work, the phone number embedded in the URL must be in the same format as the phone number is stored in SFDC. For example, 8005551212 may not match, but (800) 555-1212 will.

Only the main number for the SFDC account will match. Phone numbers for additional contacts for that account will not match.

Are we understanding all that correctly? Those last two seem pretty limiting. Any advice to share? Thanks!

Bill

We're having the same or a similar problem - we've enabled Open Networking, but get no response to the http requests. We see that no process is listening on 9080 or 9090. What should we check

Audrey - Thanks for the quick response! I've contacted our BDM.

We have a customer who is happy with its agents using their existing chat and email client, but want to switch to Avaya for voice and want to use AACC to manage the blending of contacts. Is this possible?