Cisco Cisco Expressway
n
FQDN of Expressway-E peer 1: expe1.company.com
n
FQDN of Expressway-E peer 2: expe2.company.com
n
FQDN of Expressway-E cluster: company.com
_sips._tcp.company.com. 86400 IN SRV 1 1 5061 expe1.company.com.
_sips._tcp.company.com. 86400 IN SRV 1 1 5061 expe2.company.com.
_sip._tcp.company.com. 86400 IN SRV 1 1 5060 expe1.company.com.
_sip._tcp.company.com. 86400 IN SRV 1 1 5060 expe2.company.com.
_h323ls._udp.company.com. 86400 IN SRV 1 1 1719 expe1.company.com.
_h323ls._udp.company.com. 86400 IN SRV 1 1 1719 expe2.company.com.
_h323cs._tcp.company.com. 86400 IN SRV 1 1 1720 expe1.company.com.
_h323cs._tcp.company.com. 86400 IN SRV 1 1 1720 expe2.company.com.
Note that:
n
Priorities are all the same. Only use different priorities if you have different clusters allowing failover from
one primary cluster to another (secondary) cluster. In that case the primary cluster’s peers should have one
value and the other (secondary) cluster’s peers a (larger) value.
one primary cluster to another (secondary) cluster. In that case the primary cluster’s peers should have one
value and the other (secondary) cluster’s peers a (larger) value.
n
Weights should be the same – so that there is equal use of each peer.
Checking DNS SRV settings
Checking DNS SRV settings via web interface
1. Go to
Maintenance > Tools > Network utilities > DNS lookup
.
2. Enter the SRV path in the Host field.
3. Click Lookup.
Nslookup
nslookup -query=SRV _sip._tcp.example.com
Dig
dig _sip._tcp.example.com SRV
; <<>> DiG 9.4.1 <<>> _sip._tcp.example.com SRV
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44952
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 4
;; QUESTION SECTION:
Cisco Expressway Cluster Creation and Maintenance Deployment Guide (X8.1.1)
Page 32 of 37
Appendix 4: Cluster name and DNS SRV records