Incoming VoIP Features: Difference between revisions
Content deleted Content added
| Line 89: | Line 89: | ||
===More about SRV Records=== |
===More about SRV Records=== |
||
An example of using srv records would be as follows: Say you have two VoIP servers and they have the public IPs of <code>192.0.2.50</code> and <code>192.0.2.60</code> and you want to give it the DNS name of <code inline>a-pbx.example.com</code> and <code>b-pbx.example.com</code>. |
An example of using srv records would be as follows: Say you have two VoIP servers and they have the public IPs of <code>192.0.2.50</code> and <code>192.0.2.60</code> and you want to give it the DNS name of <code inline>a-pbx.example.com</code> and <code>b-pbx.example.com</code>, and then use <code>pbx.example.com</code> as the SRV record, you'd create the following DNS records for it as follows: |
||
a-pbx.example.com. A 192.0.2.50 |
a-pbx.example.com. A 192.0.2.50 |
||
| Line 99: | Line 99: | ||
The format of the 'host' part of a SRV record is: <code> _service._protocol.name</code>. The format of the 'value' of an srv record would be in the format of: <code>priority weight port host</code> |
The format of the 'host' part of a SRV record is: <code> _service._protocol.name</code>. The format of the 'value' of an srv record would be in the format of: <code>priority weight port host</code> |
||
You can test your SRV record using 'dig' on the command line, eg: |
|||
$ dig +short srv _sip._udp.pbx.example.com |
|||
1 0 5060 a-pbx.example.com. |
|||
2 0 5060 b-pbx.example.com. |
|||
===Also Ring=== |
===Also Ring=== |
||