[asterisk-users] SIP DNS SRV

[Gareth Blades]

Those SRV records are wrong. You have to specify both servers with 
different priorities against the same hostname. You have sip and sip2 
defines with different SRV records so whichever one you configure on the 
phone thats the only record it will seen.
You should use something like this and configure the phones to use 
sip.domain.tld. :-

sip2.domain.tld.    A    YY.YY.YY.YY
sip1.domain.tld.    A    XX.XX.XX.XX

_SIP._udp.sip.domain.tld  SRV 0 1 5060 sip1.domain.tld.
_SIP._udp.sip.domain.tld  SRV 1 1 5060 sip2.domain.tld.


Jonas Kellens wrote:
> Hello,
> 
> DNS SRV is not really working: when I stop the Asterisk proces on my 
> production server, then the SIP phone is not registering to my backup 
> SIP server.
> 
> I have the following DNS records :
> 
> sip2.domain.tld.    A    YY.YY.YY.YY
> sip.domain.tld.    A    XX.XX.XX.XX
> 
> _SIP._udp.sip2.domain.tld.    SRV    YY.YY.YY.YY.
> _SIP._udp.sip.domain.tld.    SRV    XX.XX.XX.XX.
> 
> 
> _udp.sip2.domain.tld has a priority of 25
> _udp.sip.domain.tld has a priority of 5
> 
> 
> Jonas.
> 
> 
> 
> On 10/18/2010 02:03 PM, Gareth Blades wrote:
>> Yes if you set the production server to a higher priority then the 
>> backup then the RFC states that the client should periodically check and 
>> switch back to the primary server is it becomes reachable.
>>
>>
>> Jonas Kellens wrote:
>>   
>>>    Hello,
>>>
>>> I know YeaLink for example supports this...
>>>
>>>
>>> Can you tell me for sure that when the production Asterisk server 
>>> becomes reachable again, the registration will go back to the production 
>>> server ??
>>>
>>>
>>> Jonas.
>>>
>>>
>>>
>>> On 10/18/2010 01:11 PM, Gareth Blades wrote:
>>>     
>>>> Yes that is the way it is supposed to work. You do have to rely on the 
>>>> sip devices you are using fully supporting SRV records though.
>>>>