Hi Paul, 
 
You will need to set up new DNS entries and change the configuration in 
/etc/clearwater/config.

DNS:
You will need to have separate entries for your S-CSCF nodes and your I-CSCF 
nodes. The entries needed are described in detail at  
https://github.com/Metaswitch/clearwater-docs/wiki/Clearwater-DNS-Usage.

Configuration:
On the I-CSCF node you will need to change /etc/clearwater/config to include:
 - icscf=5052
 - alias_list=<icscf.domain>
 - There must not be an entry for scscf=

On the S-CSCF node you will need to change /etc/clearwater/config to include:
 - scscf=5054
- scscf_uri=<scscf.domain>:5054
 - external_icscf=<icscf.domain>:5052
- There must not be an entry for icscf=

On the Bono node you will need to change /etc/clearwater/config to include:
 - upstream_hostname=<icscf.domain>
 - upstream_port=5052

You can find more information about the different Clearwater configuration 
options at: 
https://github.com/Metaswitch/clearwater-docs/wiki/Clearwater-Configuration-Options-Reference.
 

Hope this helps, 

Ellie 

-----Original Message-----
From: Paul Sun [mailto:[email protected]] 
Sent: 02 July 2014 02:41
To: Eleanor Merry; [email protected]
Subject: RE: Problem on preparing the DNS database.

Hi Ellie

If I want to separate I-CSCF and S-CSCF, what I should do in terms of 
installation and configuration?

Thanks

- PS

-----Original Message-----
From: Eleanor Merry [mailto:[email protected]] 
Sent: Thursday, June 26, 2014 6:35 PM
To: Paul Sun; [email protected]
Subject: RE: Problem on preparing the DNS database.

Hi Paul, 

If you have the S-CSCF and I-CSCF functions on the same node, then you only 
need to set up one DNS record for it - as requests to the S-CSCF will go to 
<record>:5054 and requests to the I-CSCF will go to <record>:5052. 

Ellie

-----Original Message-----
From: Paul Sun [mailto:[email protected]] 
Sent: 24 June 2014 01:39
To: Eleanor Merry; [email protected]
Subject: RE: Problem on preparing the DNS database.

Hi Eliie

Thank for the reply. Can you elaborate more on the 2nd point? Currently, the 
I-CSCF and S-SCSF are on the same nodes (although, I would like to try to 
separate it in the future). Below is my revised config.

$TTL 5m ; Default TTL

; SOA, NS and A record for DNS server itself
@                 3600 IN SOA  ns admin ( 2014010800 ; Serial
                                          3600       ; Refresh
                                          3600       ; Retry
                                          3600       ; Expire
                                          300 )      ; Minimum TTL
@                 3600 IN NS   ns
ns                3600 IN A    1.0.0.1 ; IPv4 address of BIND server
ns                3600 IN AAAA 1::1    ; IPv6 address of BIND server

; bono
; ====
;
; Per-node records - not required to have both IPv4 and IPv6 records
bono-1                 IN A     192.168.1.212
;
; Cluster A and AAAA records - UEs that don't support RFC 3263 will simply ; 
resolve the A or AAAA records and pick randomly from this set of addresses.
@                      IN A     192.168.1.212
;
; NAPTR and SRV records - these indicate a preference for TCP and then resolve 
; to port 5060 on the per-node records defined above.
@                      IN NAPTR 1 1 "S" "SIP+D2T" "" _sip._tcp
@                      IN NAPTR 2 1 "S" "SIP+D2U" "" _sip._udp
_sip._tcp              IN SRV   0 0 5060 bono-1
_sip._udp              IN SRV   0 0 5060 bono-1

; sprout
; ======
;
; Per-node records - not required to have both IPv4 and IPv6 records
sprout-1               IN A     192.168.1.211
;
; Cluster A and AAAA records - P-CSCFs that don't support RFC 3263 will simply 
; resolve the A or AAAA records and pick randomly from this set of addresses.
sprout                 IN A     192.168.1.212
;
; NAPTR and SRV records - these indicate TCP support only and then resolve ; to 
port 5054 on the per-node records defined above.
sprout                 IN NAPTR 1 1 "S" "SIP+D2T" "" _sip._tcp.sprout
_sip._tcp.sprout       IN SRV   0 0 5054 sprout-1
;
; Per-node records for I-CSCF (if enabled) - not required to have both ; IPv4 
and IPv6 records 
sprout-3               IN A     192.168.1.211
;
; Cluster A and AAAA records - P-CSCFs that don't support RFC 3263 will simply 
; resolve the A or AAAA records and pick randomly from this set of addresses.
icscf.sprout           IN A     192.168.1.211
;
; NAPTR and SRV records for I-CSCF (if enabled) - these indicate TCP ; support 
only and then resolve to port 5052 on the per-node records ; defined above.
icscf.sprout           IN NAPTR 1 1 "S" "SIP+D2T" "" _sip._tcp.icscf.sprout
_sip._tcp.icscf.sprout IN SRV   0 0 5052 sprout-3

; homestead
; =========
;
; Per-node records - not required to have both IPv4 and IPv6 records
homestead-1            IN A     192.168.1.214
;
; Cluster A and AAAA records - sprout picks randomly from these.
hs                     IN A     192.168.1.214
;
; (No need for NAPTR or SRV records as homestead doesn't handle SIP traffic.)

; homer
; =====
;
; Per-node records - not required to have both IPv4 and IPv6 records
homer-1                IN A     192.168.1.215
;
; Cluster A and AAAA records - sprout picks randomly from these.
homer                  IN A     192.168.1.215
;
; (No need for NAPTR or SRV records as homer doesn't handle SIP traffic.)

; ralf
; =====
;
; Per-node records - not required to have both IPv4 and IPv6 records
ralf-1                IN A     192.168.1.213
;
; Cluster A and AAAA records - sprout and bono pick randomly from these.
ralf                  IN A     192.168.1.213
;
; (No need for NAPTR or SRV records as ralf doesn't handle SIP traffic.)

; ellis
; =====
;
; ellis is not clustered, so there's only ever one node.
;
; Per-node record - not required to have both IPv4 and IPv6 records
;ellis-1                IN A     7.0.0.1
;ellis-1                IN AAAA  7::1
;
; "Cluster"/access A and AAAA record
;ellis                  IN A     7.0.0.1
;ellis                  IN AAAA  7::1




-----Original Message-----
From: Eleanor Merry [mailto:[email protected]]
Sent: Monday, June 23, 2014 11:39 PM
To: Paul Sun; [email protected]
Subject: RE: Problem on preparing the DNS database.

Hi Paul, 

You don't need to replace the names - what you have below is fine. 

Two things I've seen though:
 - You're missing an IP address in the first entry for bono-1. 
 - You don't need separate I-CSCF entries if you don't have your S-CSCF and 
I-CSCF on separate nodes. 

Ellie

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Paul Sun
Sent: 23 June 2014 08:24
To: [email protected]
Subject: [Clearwater] Problem on preparing the DNS database.

Hi

I am creating a ENUM server for the Clearwater lookup, however, I have some 
confusion on preparing the bind database file. If I only have one BONO, SPROUT, 
HOMSTEAD, HOMER, what I should change? What should be the name that I should 
use to replace sprout-1, bono-1, sprout-3, homer-1, homestead-1?


-          PS


; bono

; ====

;

; Per-node records - not required to have both IPv4 and IPv6 records

bono-1                 IN A

;

; Cluster A and AAAA records - UEs that don't support RFC 3263 will simply

; resolve the A or AAAA records and pick randomly from this set of addresses.

@                      IN A     192.168.0.11

;

; NAPTR and SRV records - these indicate a preference for TCP and then resolve

; to port 5060 on the per-node records defined above.

@                      IN NAPTR 1 1 "S" "SIP+D2T" "" _sip._tcp

@                      IN NAPTR 2 1 "S" "SIP+D2U" "" _sip._udp

_sip._tcp              IN SRV   0 0 5060 bono-1

_sip._udp              IN SRV   0 0 5060 bono-1



; sprout

; ======

;

; Per-node records - not required to have both IPv4 and IPv6 records

sprout-1               IN A     192.168.0.21

;

; Cluster A and AAAA records - P-CSCFs that don't support RFC 3263 will simply

; resolve the A or AAAA records and pick randomly from this set of addresses.

sprout                 IN A     192.168.0.21

;

; NAPTR and SRV records - these indicate TCP support only and then resolve

; to port 5054 on the per-node records defined above.

sprout                 IN NAPTR 1 1 "S" "SIP+D2T" "" _sip._tcp.sprout

_sip._tcp.sprout       IN SRV   0 0 5054 sprout-1

;

; Per-node records for I-CSCF (if enabled) - not required to have both

; IPv4 and IPv6 records

sprout-3               IN A     192.168.0.21

;

; Cluster A and AAAA records - P-CSCFs that don't support RFC 3263 will simply

; resolve the A or AAAA records and pick randomly from this set of addresses.

icscf.sprout           IN A     192.168.0.21

;

; NAPTR and SRV records for I-CSCF (if enabled) - these indicate TCP

; support only and then resolve to port 5052 on the per-node records

; defined above.

icscf.sprout           IN NAPTR 1 1 "S" "SIP+D2T" "" _sip._tcp.icscf.sprout

_sip._tcp.icscf.sprout IN SRV   0 0 5052 sprout-3



; homestead

; =========

;

; Per-node records - not required to have both IPv4 and IPv6 records

homestead-1            IN A     192.168.0.31

;

; Cluster A and AAAA records - sprout picks randomly from these.

hs                     IN A     192.168.0.31

;

; (No need for NAPTR or SRV records as homestead doesn't handle SIP traffic.)



; homer

; =====

;

; Per-node records - not required to have both IPv4 and IPv6 records

homer-1                IN A     192.168.0.41

;

; Cluster A and AAAA records - sprout picks randomly from these.

homer                  IN A     192.168.0.41

;

; (No need for NAPTR or SRV records as homer doesn't handle SIP traffic.)



; ralf

; =====

;

; Per-node records - not required to have both IPv4 and IPv6 records

ralf-1                IN A     192.168.0.51

;

; Cluster A and AAAA records - sprout and bono pick randomly from these.

ralf                  IN A     192.168.0.51

;

; (No need for NAPTR or SRV records as ralf doesn't handle SIP traffic.)

_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/listinfo/clearwater
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/listinfo/clearwater

Reply via email to