[OpenSIPS-Users] DNS SRV records
Alex G
greekman0000 at gmail.com
Fri Oct 3 15:22:33 CEST 2008
is anyone else seeing a crash when they attempt to use a SRV record for
rewritehost();?
seems no matter what i do, i can't get around the crash!
anyone got a cfg file example on how it might be done differently?
really bogged down with this :(
On Tue, Sep 30, 2008 at 9:37 AM, Alex G <greekman0000 at gmail.com> wrote:
> currently using opensips-1.4.2-tls
> the dns is indeed valid. I've checked it against other nameservers on the
> net other than our provider's name server
>
> there's nothing fishy in my config file either. Pretty straight forward
> routing. As you can see in the ngrep cap below, the SRV record is returning
> the A records for the domains in it.
>
> Any help is always appreciated :) Thanks
>
> Alex
>
>
>
> On Tue, Sep 30, 2008 at 6:41 AM, Bogdan-Andrei Iancu <
> bogdan at voice-system.ro> wrote:
>
>> Hi Alex,
>>
>> What is the domain name you were trying? is the DNS still valid (like SRV
>> records) for it ? What opensips version are you using?
>>
>> I want to try to reproduce the crash and to work out a fix.
>>
>> Thanks and regards,
>> Bogdan
>>
>> Alex G wrote:
>>
>>> trying the domain without the prefixes got me this:
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22080]: CRITICAL:core:receive_fd:
>>> EOF on 19
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22004]: INFO:core:handle_sigs:
>>> child process 22034 exited by a signal 11
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22004]: INFO:core:handle_sigs:
>>> core was generated
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22004]: INFO:core:handle_sigs:
>>> terminating due to SIGCHLD
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22080]: INFO:core:sig_usr: signal
>>> 15 received
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22065]: INFO:core:sig_usr: signal
>>> 15 received
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22044]: INFO:core:sig_usr: signal
>>> 15 received
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22046]: INFO:core:sig_usr: signal
>>> 15 received
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22071]: INFO:core:sig_usr: signal
>>> 15 received
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22076]: INFO:core:sig_usr: signal
>>> 15 received
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22062]: INFO:core:sig_usr: signal
>>> 15 received
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22042]: INFO:core:sig_usr: signal
>>> 15 received
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22054]: INFO:core:sig_usr: signal
>>> 15 received
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22015]: INFO:core:sig_usr: signal
>>> 15 received
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22061]: INFO:core:sig_usr: signal
>>> 15 received
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22040]: INFO:core:sig_usr: signal
>>> 15 received
>>> Sep 29 19:06:34 openser1 /sbin/opensips[22064]: INFO:core:sig_usr: signal
>>> 15 received
>>>
>>> proxy completely crashed!
>>>
>>> ngrep on port 53 shows its getting back a records:
>>>
>>> U 64.94.60.251:37320 <http://64.94.60.251:37320> -> 69.25.1.1:53 <
>>> http://69.25.1.1:53>
>>> .............wholesaleorigination.acc.globalipcom.com..#..
>>>
>>> U 69.25.1.1:53 <http://69.25.1.1:53> -> 64.94.60.251:37320 <
>>> http://64.94.60.251:37320>
>>> .............wholesaleorigination.acc.globalipcom.com..#...!.........
>>> 3.auth00.ns.uu.net <http://3.auth00.ns.uu.net>.
>>> hostmaster.P......T`......^...T`
>>>
>>> U 64.94.60.251:37320 <http://64.94.60.251:37320> -> 69.25.1.1:53 <
>>> http://69.25.1.1:53>
>>> .............wholesaleorigination.acc.globalipcom.com..#..
>>>
>>> U 69.25.1.1:53 <http://69.25.1.1:53> -> 64.94.60.251:37320 <
>>> http://64.94.60.251:37320>
>>> .............wholesaleorigination.acc.globalipcom.com..#...!.........
>>> 3.auth00.ns.uu.net <http://3.auth00.ns.uu.net>.
>>> hostmaster.P......T`......^...T`
>>>
>>> U 64.94.60.251:37320 <http://64.94.60.251:37320> -> 69.25.1.1:53 <
>>> http://69.25.1.1:53>
>>> *............_sip._udp.wholesaleorigination.acc.globalipcom.com..!..
>>>
>>> U 69.25.1.1:53 <http://69.25.1.1:53> -> 64.94.60.251:37320 <
>>> http://64.94.60.251:37320>
>>>
>>> *............_sip._udp.wholesaleorigination.acc.globalipcom.com..!.....!....T..1.d.2...wholesaleoriginationd.acc.globalipcom.com....!....T..1.d.2...wholesaleoriginationa.acc.globalipcom.com....!....T..1.d.2...wholesaleoriginationb.acc.globalipcom.com....!....T..1.d.2...wholesaleoriginationc.acc.globalipcom.com..#......T....auth00.ns.uu.net..#......T..
>>>
>>> .auth100.K........T...A.x.........T...A...........T...?ML..V......T...A.(..D.............A.b.......0......
>>>
>>>
>>>
>>> On Mon, Sep 29, 2008 at 6:14 PM, Sergio Gutierrez <saguti at gmail.com<mailto:
>>> saguti at gmail.com>> wrote:
>>>
>>> Hi Alex.
>>>
>>> Try this:
>>>
>>> rewritehost("wholesaleorigination.acc.globalip.com
>>> <http://wholesaleorigination.acc.globalip.com>");
>>> rewriteport("");
>>> t_relay();
>>>
>>> Best regards.
>>>
>>> Sergio G.
>>>
>>>
>>> On Mon, Sep 29, 2008 at 5:04 PM, Alex G <greekman0000 at gmail.com
>>> <mailto:greekman0000 at gmail.com>> wrote:
>>>
>>> hi sergio,
>>>
>>> the SRV record is for my pstn gateway. I'm placing the SRV
>>> record in
>>> rewritehostport("_sip._
>>> udp.wholesaleorigination.acc.globalipcom.com
>>> <http://udp.wholesaleorigination.acc.globalipcom.com/>");
>>> like this prior to my t_relay. opensips log is showing me the
>>> errors i posted below. I didn't think something special was
>>> needed, but it doesn't seem to work as it should.
>>>
>>> nslookup of the SRV record on the local machine shows that its
>>> there and it returns several A records.
>>>
>>> i'm very stumped on this one... any help would be much
>>> appreciated :)
>>>
>>> also the DNS i am hitting is our internet provider's dns,
>>> which like i said the SRV records seem to resolve at when
>>> using nslookup.
>>>
>>> Alex
>>>
>>>
>>> On Mon, Sep 29, 2008 at 5:50 PM, Sergio Gutierrez
>>> <saguti at gmail.com <mailto:saguti at gmail.com>> wrote:
>>>
>>> Hi Alex.
>>>
>>> OpenSIPS does not need any special setup to resolve SRV
>>> recrds.
>>>
>>> How do you have defined your SRV records at DNS config?
>>>
>>> If wholesaleorgination.acc.globalipcom.com
>>> <http://wholesaleorgination.acc.globalipcom.com> is a SRV,
>>> you just call the function you need, t_relay or forward,
>>> and your uri fould read as
>>> username at wholesaleorgination.acc.globalipcom.com
>>> <mailto:username at wholesaleorgination.acc.globalipcom.com>
>>>
>>> Best regards.
>>>
>>> Sergio G.
>>>
>>> On Mon, Sep 29, 2008 at 3:44 PM, Alex G
>>> <greekman0000 at gmail.com <mailto:greekman0000 at gmail.com>>
>>> wrote:
>>>
>>> is there anything special i need to do in the config
>>> file to use SRV records? I try to rewritehostport to
>>> the dns srv record but i cannot seem to resolve:
>>>
>>> Sep 29 16:40:10 openser1 /sbin/opensips[21292]:
>>> CRITICAL:core:mk_proxy: could not resolve hostname:
>>> "_sip._udp.wholesaleorigination.acc.globalipcom.com
>>> <http://udp.wholesaleorigination.acc.globalipcom.com>"
>>> Sep 29 16:40:10 openser1 /sbin/opensips[21292]:
>>> ERROR:tm:uri2proxy: bad host name in URI
>>> <sip:+14016411072 at _sip._
>>> udp.wholesaleorigination.acc.globalipcom.com:5060
>>> <http://udp.wholesaleorigination.acc.globalipcom.com:5060
>>> >>
>>>
>>>
>>> have tried with and without defining the port and
>>> still no luck
>>>
>>> i even turned on ipv6 checks if ipv4 fails and still
>>> no luck.
>>>
>>>
>>> what am i missing here?
>>>
>>>
>>> Thanks,
>>>
>>> Alex
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org <mailto:Users at lists.opensips.org
>>> >
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20081003/271760b8/attachment-0001.htm
More information about the Users
mailing list