UCA client and new Border gateway

[pkriek]

Hi

In our datacanetr 1 we have the mitel servers, with MAS MCD and a seperate border gateway. All is working okay. Including teleworker phones and UA softphones.

Now we instaled in a second datacenter a new Border gateway. Teleworker phones are working when connecting to this server, but not the UCA softphones. They connect, but its unable to call and the statusses are not coming thru. Certifcate stuff is working.

troubelshooting shows that we can make it to work internally when adapting the UCA.EXE.CONFIG file on the client pc. when we change th FQDN of the server under YAsettings, see where I put x.x.x.x. If we change those to the MAS server , whcich is reachable internaly and by using a VPN connection. Then the client works like a charm.

 <YASettings>
    <add key="language" value="en-US"/>
    <add key="WebServicesHost" value="x.x.x.x"/>
    <add key="WebServicesPort" value="80"/>
    <add key="TelephonyServerIP" value="x.x.x.x"/>
    <add key="TelephonyServerPort" value="80"/>
    <add key="SipTransport" value="tcp"/>

Teleworker IP , we leave that in the client pointing to the public IP of the border gateway 2.

Does anybody have an idea how we can solve this??

thanks

[pkriek]

SipGateway: Received Registration result: Timeout, current state: False, current registrationState=Failed_Timeout, isOffline=True

In the UCA client logs , we see this repeating

[martyn]

If you run the TNA tool against the IP address of the problem MBG does it show the UCA/YA ports as being open?

[pkriek]

yes al ports okay