from what i've read and come to understand....sip over tcp and udp are the same port by default (5060)......it's the secure sip signalling implementation (called tls aka cousin or big brother to ssl v3.0) that uses 5061 by default........i think the 5060 (tcp/udp) and tls (5061) can be changed on the server that runs the process simply by telling the server to run on another port number.....just like you can run a www server on 81 or 8080 or whatever......then simply hit it from the client (http browser) as http://www.domain.com:81 <http://www.domain.com:81> or http://www.domain.com:8080 <http://www.domain.com:8080> or in sip terminology..... sip:[EMAIL PROTECTED]:5060 or sips:[EMAIL PROTECTED]:5061 or sip(s):[EMAIL PROTECTED]:5066 whatever......but remember your dns administrator is the one who will put the port number that your asterisk (sip server) is running (listening) on into the srv dns record. .....whether it's 5060 (udp/tcp) or 5061 (tls) or a non-standard 5090 or whatever. also you can check to see when your dns go has done his job by testing with nslookup at the command line of your unix or pc box.... nslookup set type=srv _sip._udp.oegema.com should return something about the SRV service record pri, wght, port#, srv hostname (or in your case probably ip address 81.164.185.132) but if it were a hostname, then under that also would show hostname to ip resolution... if you don't get a response then perhaps the dns isn't update propoerly or at all. i think there is some sort of serial number (dns update or zone transfer) timer that needs to be altered to kickoff dns to update........i'm reaching here......i can't remember
________________________________ From: Henk Oegema [mailto:[EMAIL PROTECTED] Sent: Fri 6/23/2006 9:09 AM To: Gould, Aaron; [email protected] Cc: [EMAIL PROTECTED] Subject: RE: [Sip-implementors] SRV record creation Dear Aaron First of all I want to say that I am very greatfull for getting a reply. As I mentioned in my mail, I have only theoritical knowledge of SRV records. I actually learned it from the website which you mentioned in your reply.(http://mit.edu/sip/sip.edu/dns.shtml <http://mit.edu/sip/sip.edu/dns.shtml> ) That was the template I used to create mine. :-) henkoegema.ftpaccess.cc is NOT the ip adress of my Asterisk server. My Asterisk server has a dynamic ip address. henkoegema.ftpaccess.cc is a DynDNS pointer to my Asterisk server. I have changed my proposal as follows (according to your input) ************************************************************** oegema.com. IN SOA ns1.ascio.net. hostmaster.ascio.net.( 20060613000 10800 5400 3600000 14400 ) oegema.com. 166214 IN NS ns1.ascio.net. ; ns1.ascio.net. 155412 IN A 80.82.97.156 ; _sip._udp.oegema.com. 43200 IN SRV 0 0 5060 81.164.185.132 _sip._tcp.oegema.com. 43200 IN SRV 0 0 5060 81.164.185.132 *************************************************************** I am still not sure if the port number for udp and tcp can be the same or must be different. In Jeremy's example all port numbers are the same. 81.164.185.132 is my ip address (at the moment.) I only put it there to know if the record is syntacticly correct. The issue with the dynamic address has to be solved by my domain provider.(which he said he could) What do you think of it now??? Thanks and regards Henk -----Oorspronkelijk bericht----- Van: Gould, Aaron [mailto:[EMAIL PROTECTED] Verzonden: vrijdag 23 juni 2006 16:50 Aan: [EMAIL PROTECTED]; [email protected] CC: [EMAIL PROTECTED] Onderwerp: RE: [Sip-implementors] SRV record creation i have limited knowledge of this, but do have both sip over tcp and udp working in my lab using dns in your entries below, i don't think you should have the username "henk" included in the dns domain name......i beleive the way you have it listed is as if "henk" were a subdomain of the domain "oegema.com".... also, the way i did it was with a hostname of the sip registrar/proxy where you have xxxxxx's but it might also be valid to use the ip address. i'm not sure. but you mentioned something about a dynamic address....if that is subject to change then you won't want to use that as the point of reference.....if the name "henkoegema.ftpaccess.cc" is the name of your asterisk box and it doesn't change but only the ip address changes, then you would want to use that _sip._udp.henk.oegema.com. 43200 IN SRV 0 0 5060 xxxxx.xxx.xxx (??) _sip._tcp.henk.oegema.com. 43200 IN SRV 0 0 5060 xxxxx.xxx.xxx (??) i think it should look like this..... _sip._udp.oegema.com. 43200 IN SRV 0 0 5060 henkoegema.ftpaccess.cc _sip._tcp.oegema.com. 43200 IN SRV 0 0 5060 henkoegema.ftpaccess.cc just to make sure, i'm assuming henkoegema.ftpaccess.cc is your asterisk box. jeremy george from yale did a nice write-up on this subject. see link below. also, you may want to have your provider put in the sips: entries to allow sip over tls over tcp for secure/encrypted communications.......even if you don't need it currently at least the dns entries will be there for later use when you fire up those tls services (ua's and prox/regis servers)....also keep your eye out for dtls (tls over udp) .....if anyone knows the dns and udp port number that is envisioned for that please share. also if anyone understands the "_outboundsip....." dns thing, please explain what it's used for. see rfc 2782 if you wish also http://mit.edu/sip/sip.edu/dns.shtml <http://mit.edu/sip/sip.edu/dns.shtml> ....jeremy, in your write-up did you intend for the tcp port number in the following entries to be 5060, or should it have been 5061.? thanks _sips._tcp.bigu.edu. 43200 IN SRV 0 0 5060 sipserver1.bigu.edu. _sips._tcp.bigu.edu. 43200 IN SRV 0 0 5060 sipserver2.bigu.edu. aaron p.s. someone correct me if i'm misled on any of my comments above ________________________________ From: [EMAIL PROTECTED] on behalf of Henk Oegema Sent: Fri 6/23/2006 3:37 AM To: [email protected] Subject: [Sip-implementors] SRV record creation I have asked this question at two different forums but not get any reply at both of them. That why I hope to find a solution here. If this is not the right place to ask, please forgive me. My domain provider is willing to create a SRV record in the DNS server, for routing sip calls (sip:[EMAIL PROTECTED]) to my Asterisk server. This is what the provider wrote me: ================================================================================= Dear Henk Oegema Thank you for contacting us. We cannot help you to setup your SRV record, this is not a service we provide our customers, if you want to have a SRV record, you have to tell us what info you want to enter, then we will enter exactly that information (Corrected so it fits our nameservers of course), but we do not offer to help you figure out what your SRV record should look like. ================================================================================= Because I don't have access to that server, the SRV record has to be correct straight from the start, to avoid multiples mails from me to my domain provider. (and I have never done this before) Here is some data from my system: 1. My server has a dynamic address, updated by a DynDNS server. (henkoegema.ftpaccess.cc). According to the domein provider this could be used. 2.Domain: henk.oegema.com 3. Sip calls have to be routed to sip:[EMAIL PROTECTED] I think (but please correct me) that such a record is as follows: ************************************************************** henk.oegema.com. IN SOA ns1.ascio.net. hostmaster.ascio.net.( 20060613000 10800 5400 3600000 14400 ) henk.oegema.com. 166214 IN NS ns1.ascio.net. ; ns1.ascio.net. 155412 IN A 80.82.97.156 ; _sip._udp.henk.oegema.com. 43200 IN SRV 0 0 5060 xxxxx.xxx.xxx (??) _sip._tcp.henk.oegema.com. 43200 IN SRV 0 0 5060 xxxxx.xxx.xxx (??) *************************************************************** (ns1.ascio.net is the name of the DNS server containg the record) Questions: ------------------ 1. Has the entry in the SRV record to be 'henk.oegema.com.' or just 'oegema.com.' (without: henk) 2. Where (and how) is my dynamic ip address coming in the picture (via henkoegema.ftpaccess.cc) ?? 3. Suppose I had a static ip address of 81.164.185.132. are the lines: _sip._udp.henk.oegema.com. 43200 IN SRV 0 0 5060 81.164.185.132 _sip._tcp.henk.oegema.com. 43200 IN SRV 0 0 5060 81.164.185.132 than correct? 4. Do I need both _sip._udp. and _sip._tcp. (or is _sip._udp enough ?) I am sure there are (a lot?) mistakes here, because I have only theoretical knowledge about this issue and never tested it in practice. (with trial and error) Thanks for any advise Regards Henk Oegema http://www.henk.oegema.com e-mail: [EMAIL PROTECTED] sip: [EMAIL PROTECTED] (This is what I want to achieve !) _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
