Hi Henk,
As far as my limited knowledge about this is concerned I have put in some lines into your mail.
regards
Rayees
To: [email protected]
From: Henk Oegema <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
Date: 06/23/2006 11:37AM
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 (??)
***************************************************************
[RK] the xxxxx.xxx.xxx here should be henk.oegema.com and you do need both _udp and _tcp records if your server is supporting both types of services.
(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)
[RK} Yes it should be henk.oegema.com
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?
[RK] Yes it should be though I have never tried that. I normally put in some name and insert an A-record for the same name
4. Do I need both _sip._udp. and _sip._tcp. (or is _sip._udp enough ?)
[RK] Depends on the services that your server is providing if it is both UDP and TCP then, yes, both are required.
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
*****FSS-Private *****" DISCLAIMER: This message is proprietary to Flextronics Software Systems Limited (FSS) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSS accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
_______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
