Avaya Communicator 2.1.4.0 Build 256 1

[slim187m]

Anyone run into an issue where Avaya Communicator - Telephony only (NO one-X Portal) successfully Loads Contacts when locally connected to the network, but does not load them when Remote? Just says Loading contacts...
Is this possibly a TCP/UDP port issue?
Everything else that's supposed to work with "Telephony only" works but this.
Thanks if anyone has any answers...

 

[CASSBusinessSystems]

Make sure all of the ports are forwarded and allowed in your firewall.

Here are the ports:

tcp 8069
tcp 5222
tcp 5269
tcp 8444
tcp 50814
tcp 8666
tcp 8063
tcp 8443
tcp 9443
tcp 80
tcp 21
tcp 8080
udp [RTP range]
tcp 5060

Hope this helps!

 

[slim187m]

alright, I'll try all those and narrow it down and will post back.
Thanks CASS!

 

[slim187m]

Tried 'em all, didn't work. Thanks again

 

[holdmusic34]

you're using an fqdn right?

Try to spend the next 10 seconds not thinking about a blue eyed polar bear.

 

[CASSBusinessSystems]

^ Good point, make sure you have set the FDQN on the LAN interface of the IP Office and in the One-X Portal (under IM/Presence configuration) configuration. Also make sure your split DNS is setup properly.

 

[slim187m]

Okay, maybe that's what it is...
I only had SIP Domain Name entered, and not SIP Registrar FQDN. Looks like I'll have to study up to see how that works. I'm guessing I'll have to get a sub-domain pointed to the IPO??

 

[slim187m]

Also as a side-note, remember I'm not using one-X Portal. This is just a Telephony-only solution

 

[CASSBusinessSystems]

In LAN interface, set SIP domain to onex.company.com.

Public DNS should resolve onex.company.com to the public address being port forwarded to the IPO. Internal DNS should resolve onex.company.com to the LAN address of the IPO.

Hope this helps.

 

[slim187m]

yeah I'm so unfamiliar with the concept of DNS in this setup. I don't know what the purpose of the public and private DNS involved and how they come into play here. I'm thinking if trying to access through the internet, I'll have to get a publicly accessible sub-domain to point to the public IP of the IPO. Privately, the internal DNS with the router will be able to resolve...??

 

[amriddle01]

The post above yours explains it quote well ?

 

[slim187m]

Ok, correct me if I'm wrong.
Went to Godaddy, setup a subdomain to point to the public IP address of the IPO. - Not sure if this was required, but seemed logical to get remote communication using name for seamless roaming.
In Manager, set SIP Domain Name in LAN interface to the domain - <company>.com. Also set SIP Registrar FQDN to - ipo.<company>.com
In Communicator, set Server address to - ipo.<company>.com | Proper Server port | Domain as - <company>.com
All works the same, still no Contacts. Continues to say "Loading contacts."
Unsure where to go to get the internal DNS to resolve to the IPO LAN address though as this site doesn't have a local DNS server

 

[slim187m]

Well got it working. Seems forwarding port 80 worked. However I had that pointing to the IPO before...I can't imagine setting up the SIP Registrar FQDN is what also did the fix though, but what do I know...
No longer "Loading contacts." All local Contacts are available now
Thanks everyone, particularly CASS!