From: Henk Oegema <[EMAIL PROTECTED]> 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]
To simplify: you want all calls to sip:[EMAIL PROTECTED] to be sent to the server named henkoegema.ftpaccess.cc. Note that the SRV process will not look at or modify the user-part of a SIP URI. In fact, SRV will not change the request-URI of a request at all; it only specifies where the request will be sent. The steps you need to take are: 1) Ensure that your ISP is the DNS server for the domain henk.oegema.com. 2) Ensure that the SIP server at henkoegema.ftpaccess.cc is prepared to correctly route any incoming SIP request with request-RUI sip:[EMAIL PROTECTED] to the proper place. (Where or how it routes such requests is limited only by the server's capabilities.) 3) Provide your ISP with the SRV records. You don't have to supply an NS record for henk.oegema.com, that has been done already when the ISP set up DNS for henk.oegema.com. You shouldn't supply an A record for ns1.ascio.net -- the ISP owns ns1.ascio.net, and will have done that already. The records you need will look like this: ; Service Proto. Name Pr Wt Port Target _sip._udp.henk.oegema.com. 43200 IN SRV 0 0 5060 henkoegema.ftpaccess.cc _sip._tcp.henk.oegema.com. 43200 IN SRV 0 0 5060 henkoegema.ftpaccess.cc The Target field is allowed to be a DNS host name, so "henkoegema.ftpaccess.cc" will be mapped by the A record to its current address whenever this SRV record is used. The Weight field can be 0 since you have only one SRV record for each protocol (UDP or TCP). (If you had more than one, Weight should be non-0 to avoid anomalies in the RFC 3263 algorithm that are likely to be implemented incorrectly.) The Name field is "henk.oegema.com" because these SRV records are to route requests for sip:[EMAIL PROTECTED] Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
