Issue: When installing FMG as part of an on-premise Connect deployment, the fresh installation of FMG includes many default profiles in the sip. xml file. When you enter values from Connect console (port 8510 locally on the server), those values are populated to the first profile that is listed in sip.xml (sipPhone) and not to the correct sipGateway profile which is called from the workflow.xml file.
The expected behavior is that the values from Connect console should update the sipGateway profile rather than the first profile in sip.xml
Workaround: The Adobe Connect Support team is using currently approaching this problem from one of two possible ways:
- You may copy a sipGateway profile from a vertsion of FMG prior to version 2.x and paste that into FMG 2.x.
- You may call sipPhone profile from workflow.xml
Note: In FMG prior to version 2.x, sipGateway was the first profile listed in sip.xml. The workflow.xml file checks the input number and on the basis of that chooses the profile from sip.xml. With default FMG settings it will be using ‘SipGateway’ most of the time. This is scheduled to be fixed in Connect 9.3.