Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

communicator presnece issue

Status
Not open for further replies.

maccabee333

Programmer
Aug 17, 2009
130
GB
HI Chaps,

Going crazy with this one. I have Communicator connecting through my SBC to IPO. Works fine. However when it registers the one-x info the IPO sends out is wrong its sending the IP of the one-x/serverEd.

The one-x has a godaddy cert and the XMPP is correct. No issues with one-x mobile when the reverse is applied and it connects to one-x and gets sent the SBC FQDN.

I have tried changing the one-x ip in web manager to the public but still just internal. Does anyone know if this is split DNS issue and the ipo is resolving the FQDN to its internal address instead of external.

Any suggestions would be great.

no go on 9.1.5 now on 9.1.7 still doesnt work.
 
Read about that two days before... So you are the luck one ;-)

You have to enter the external resolvable FQDN of your IPO server in the SBC config as call server address. If you enter the internal IP instead IPO will send that IP back to communicator during SIP registration.
 
hadnt thought to look there. Thanks ill give this ago and let you know the outcome.

IP Office - APSS,AIPS,ACIS,ACSS
IP Office Contact Center - ASPS
SpliceCom Advanced Specialist

follow me on Twitter @TheIanMac
 
That didnt change a thing. not sure whats going on but what ever i change, I only get the internal IP. no FQDN or external IP.

 
I fond this and its the same issue. thread940-1752306

Does anyone know how this is altered. I tried changing the PTR records in the DNS but made no difference so i dont think its that.

Thanks,

 
Anyone having this issue. It can be solved if using an SBC. Use the toplogy hiding profiles to change the to and from headers to the FQDN used in your VOIP settings on the IPO. It will the register as an external user and the correct FQDN will be sent. Having said that I have made my VOIP domain the same as the XMPP. If I use SRV records and bypass the SBC The presence is shown correctly. If using the SBC without the topology hiding. The SBC will present the registration with IP and not FQDN matching the VOIP domain. This will mean the IPO will send the local IP of one-x.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top