Hello, Maybe the problem is that there is no ip address for fenet2.at. SER does SRV lookup and then normal A lookup for the name provided in SRV's RR. I cannot see from the code if there is used NAPTR, actually the function for parsing such a RR is present but such a lookup is not performed.
The name resolution is done using gethostbyname anyway, even it tries first SRV lookup or not.
Quoting Daniel-Constantin Mierla daniel@voice-system.ro:
Hello,
it should do SRV lookup and if it gets some RR it uses them. Try to watch the DSN traffic for you sip server with "ngrep port 53".
Also you can check with "host -t srv _sip._udp.fenet2.at" if the DNS server returns correctly the SRV records. Only in the case no SRV record is returned, the openser tries normal DNS lookup.
Another option is to set openser in debug mode (log_stderror=yes and debug=7) and watch the messages or send them to me to analyze them.
Daniel
On 09/01/05 22:45, Franz Edler wrote:
Hi,
I have a question regarding the behavior of t_relay. When the proxy forwards a request for another domain using t_relay it does not use NAPTR and SRV records of the target-domain as stated in RFC3263 "Locating SIP Servers". Instead it expects a resolvable host-name for the domain-part or the URI.
The following example:
INVITE sip:andrea@fenet2.at
Causes the errors:
ERROR: mk_proxy: could not resolve hostname: "fenet2.at" ERROR: uri2proxy: bad host name in URI sip:andrea@fenet2.at ERROR: t_forward_nonack: failure to add branches
There are NAPTR and SRV RRs associated with domain "fenet2.at" but SER does not use these RRs. Why?
Are there any comments on this issue?
Regards Franz
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users