<div dir="ltr">On Tue, Jan 8, 2013 at 1:56 PM, Lawrence Conroy <span dir="ltr"><<a href="mailto:lconroy@insensate.co.uk" target="_blank">lconroy@insensate.co.uk</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi there,<br>
at the risk of butting in on someone else's party ...<br>
Nope; your interpretations is NOT best practice.<br></blockquote><div><br></div><div style>This party is open to all. I appreciate these answers, and as usual I have noticed that the fastest way to learn is to do it wrong, and then have somebody correct me! Thanks!</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
With SIP (see RFC 3263), you do a lookup on the SRV record (at _sip._udp.<sipdomain>) to find the machine that handles SIP<br>
registrations/incalls for the domain. That also gives you the port on which that machine is listening.<br></blockquote><div><br></div><div style>For example, I did a lookup:</div><div style><br></div><div style>$ dig SRV _sip._<a href="http://udp.sip.flowroute.com">udp.sip.flowroute.com</a>.<br>
</div><div style><br></div><div style>This returns:</div><div style><br></div><div style><div>_sip._<a href="http://udp.sip.flowroute.com">udp.sip.flowroute.com</a>. 43200 IN SRV 20 10 5060 <a href="http://sip-ca1.flowroute.com">sip-ca1.flowroute.com</a>.</div>
<div>_sip._<a href="http://udp.sip.flowroute.com">udp.sip.flowroute.com</a>. 43200 IN SRV 10 10 5060 <a href="http://sip-nv1.flowroute.com">sip-nv1.flowroute.com</a>.</div><div><br></div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
(Yup, you can also have a NAPTR record in the domain to tell you where the SRV record is, but many folks don't bother -- for Best Practice, you should, but ...)<br></blockquote><div><br></div><div>$ dig NAPTR <a href="http://sip.flowroute.com">sip.flowroute.com</a></div>
<div><br></div><div><a href="http://sip.flowroute.com">sip.flowroute.com</a>. 42818 IN NAPTR 100 10 "s" "SIP+D2U" "" _sip._<a href="http://udp.sip.flowroute.com">udp.sip.flowroute.com</a>.</div>
<div><a href="http://sip.flowroute.com">sip.flowroute.com</a>. 42818 IN NAPTR 102 20 "s" "SIP+D2U" "" _sip._<a href="http://tcp.sip.flowroute.com">tcp.sip.flowroute.com</a>.</div>
<div><br></div><div style>I found that _sip._<a href="http://tcp.sip.flowroute.com">tcp.sip.flowroute.com</a> does not have a SRV record. I don't know what that means. The RFC says that you should use "SIP+D2T" for TCP.</div>
<div style><br></div><div style>Now, as this relates to the Polycom phone example, there are these fields:</div><div style><br></div><div style><div> reg.1.address="1000@fs.domain.local"</div><div> reg.1.auth.userId="1000"<br>
</div><div> reg.1.server.1.address="10.10.10.11"<br></div><div> reg.1.server.1.port="5060"</div><div><br></div><div style>Since this is a VoIP phone that loads its configuration from the server, not VoIP software that is configured by the user, it really only needs the IP address, so the server address field is kind of moot.</div>
<div style><br></div><div style>But the example domain here is "fs.domain.local". Why not just "domain.local"? Why didn't Flowroute use "<a href="http://flowroute.com">flowroute.com</a>" instead of "<a href="http://sip.flowroute.com">sip.flowroute.com</a>"?</div>
<div style><br></div><div style>And my other question was how is the address "1000@fs.domain.local" used? Does FreeSwitch use that or does it just use the auth.userId?</div><div style><br></div><div style>-- </div>
<div style>Steve</div></div></div></div></div>