Yes, its resolvable as a SRV record. host -t SRV _sip._udp.phonetest.psu.edu _sip._udp.phonetest.psu.edu has SRV record 20 1 5060 os2.phonetest.psu.edu. _sip._udp.phonetest.psu.edu has SRV record 10 1 5060 os1.phonetest.psu.edu.
But it looks like its trying to do A lookup instead? Jun 2 15:17:30 os2 /sbin/opensips[13819]: DBG:core:sip_resolvehost: has port -> do A record lookup! Jun 2 15:17:30 os2 /sbin/opensips[13819]: ERROR:drouting:add_dst: cannot resolve <phonetest.psu.edu> Jun 2 15:17:30 os2 /sbin/opensips[13819]: ERROR:drouting:dr_load_routing_info: failed to add destination id 3 -> skipping Sven On 6/2/10 2:36 PM, "Bogdan-Andrei Iancu" <[email protected]> wrote: > Hi Sven, > > is "phonetest.psu.edu" valid (resolvable) in DNS ? try enabling full > debug (debug=6) and see the previous debug messages from the DNS resolver. > > Regards, > Bogdan > > Sven Schulz wrote: >> As a test, I tried to add a SRV record as a gateway into the database. >> Upon reloading drouting I got this error: >> >> Jun 1 15:50:56 testsip1 /sbin/opensips[2069]: ERROR:drouting:add_dst: >> cannot resolve <phonetest.psu.edu> >> Jun 1 15:50:56 testsip1 /sbin/opensips[2069]: >> ERROR:drouting:dr_load_routing_info: failed to add destination id 20 >> -> skipping >> >> Dest ID #20 is that SRV record. So does this mean that I cant use SRV >> records as gateways in drouting? >> >> >> Sven Schulz >> Penn State University >> Telecommunications and Network Services >> 814.865.6116 >> sip:[email protected] >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
