Lync Federation For Additional Supported Sip Domains

As you know for federation there is srv record _sipfederationtls._tcp.domain.com.     and you must create this record if you want that other organization can find your edge server (Access Edge service(FQDN)). In my experience thare was a moment when i need to make federation for additional supported sip domain (not Default sip domain), in this moment we have situation when edge fqdn domain and sip domain is different. for example we have default domain domain.com, edge FQDN  sip.domain.com and in this topology we have additional supported SIP domain additionaldomain.com

 

supp

so if you make srv record _sipfederationtls._tcp.domain.com.  it will work and other organizations will federate to you (domain.com) without Access Edge Service FQDN

 

 

picture for your partner organization that need federation to you

supp1

but if you make _sipfederationtls._tcp.additionaldomain.com. record your partner cannot federate automatically( additionaldomain.com ), your federated partner must manually add Access edge Service FQDN

sup2

Thanks :)

Add comment

  Country flag

biuquote
  • Comment
  • Preview
Loading

About the author

Giorgi Jambazishvili
System Administrator
Ministry of Justice of Georgia